Wrapping my head around this DNS issue with AdGuard add-on, anyone done this?

I get it. You run AdGuard, point your router to the AdGuard setup, then tell AdGuard where to get DNS information from. AdGuard becomes the checkpoint.

Here’s where I get stuck.

I run a UDMPro (Unifi Dream Machine Pro). All of my client devices are assigned the UDMP’s IP address as the DNS server.

In order to implement AdGuard, I would normally change the DNS settings in the DHCP server to force all local machines to run through AdGuard first (i.e. my HA instance), then AdGuard would point back to some public DNS server like Google, etc.

If I do that, I lose the ability to address local machines by their hostname. For example, my name server, which is public, is ns1. To login to my name server, all I have to do is type ssh ns1 and bam! I’m in. To connect to unraid, I simply map a volume to smb://tower.

I don’t want to use IP addresses to get to these machines.

How can I configure the network such that I don’t lose this ability if I’m pointing everything to AdGuard?

Point udmpro to adguard an adguard to internet :man_shrugging:?

That will not work unless Adguard is also the DHCP server (how would it know the hostname otherwise?)
If so, the local domain is “.lan”, so you would be able to use “ns1.lan”.

I know this is old, but I’ve found a solution to this.
In the upstream DNS servers setting one can tell adguard to redirect .local, .lan requests to the UDM or the DHCP server.
To fix the .lan requests you can use [/lan/]192.168.1.1:53

Hello @joem

Just replaced my ddwrt router with the the Dream Machine Pro. I have Adguard Home addon running in HAOS. Wirh my ddwrt router all did ( if memory serves me right) was jusr put the HAOS ip address in the first dns server option in the router. With the dream machine I have no idea where this is or even how to do this. Would you happen to know?

Thanks