3006.102.4 - DNS Director New Redirect With "Router" NOT Working

[salieri]

Router = BE86U
Firmware = 3006.102.4

- CHANGED: Setting DNS Director to "Router" will now always
redirect to the router's own IP. Previously it
would redirect to the first DNS server configured
on the DHCP page (which defaults to the router
itself).
If you need DNS Director to redirect to an IP
configured in your DHCP settings, use a Custom DNS
entry in DNS Director. This makes it more consistant
with what the name implies, and was also necessary
for improved Guest Network support.

---

I left my old DNS Director settings after the upgrade (see screenshots below).

1) The updated change is NOT redirecting to the Router's own IP. Instead it has the old behavior of redirecting using the specified DNS Server in LAN -> DHCP Server.

2) All of my devices are experiencing this.

To reproduce:
1) Used my iPhone
2) Did a Forget This Network in WiFi settings
3) Rejoined the WiFi network and entered my credentials.
4) On the iPhone I went to Configure DNS and saw the DNS Server is still 192.168.2.2

How do I get this to work?

---

 

[bennor]

4) On the iPhone I went to Configure DNS and saw the DNS Server is still 192.168.2.2

Which is expected behavior due to having the DHCP Server DNS configured for 192.168.2.2 and your phone obtaining it's IP (and DNS server) from the router's DHCP server.

How are you determining that the DNS Director isn't working? In otherwards that DNS requests are not being routed to the router. What is the router's IP address? What is the 192.168.2.2 IP address?

 

[iTyPsIDg]

FWIW, this is my setting under LAN - DHCP Server:

Spoiler: LAN - DHCP Server

DNS Director does state, '"Router" will force clients to use the DNS provided by the router's DHCP server (or, the router itself if it's not defined).' That sounds like you are seeing expected behavior. You aren't advertising your router's IP and you do have a custom DNS listed.

 

[dave14305]

DNS Director does state, '"Router" will force clients to use the DNS provided by the router's DHCP server (or, the router itself if it's not defined).' That sounds like you are seeing expected behavior. You aren't advertising your router's IP and you do have a custom DNS listed.

The behavior of Router mode changed in 3006.102.4, compared to 3004.388.9.

 

[iTyPsIDg]

The behavior of Router mode changed in 3006.102.4, compared to 3004.388.9.

My bad, I see that in the other screenshot now. I was looking at my view. Thank you!

 

[salieri]

Which is expected behavior due to having the DHCP Server DNS configured for 192.168.2.2 and your phone obtaining it's IP (and DNS server) from the router's DHCP server.

How are you determining that the DNS Director isn't working? In otherwards that DNS requests are not being routed to the router. What is the router's IP address? What is the 192.168.2.2 IP address?

Router = 192.168.2.1
AdGuard Home Server = 192.168.2.2

The wording in the changelog is confusing for me.

I took this to mean that if DNS Director is enabled, it will redirect to the Router's IP regardless of what is put on the DHCP -> DNS Server 1 page.

The changelog states that to redirect an IP using DNS Director, I should create a user-defined DNS entry instead.

I don't understand why this phrasing would be included in the changelog if it didn't do something different.

- CHANGED: Setting DNS Director to "Router" will now always
redirect to the router's own IP. Previously it
would redirect to the first DNS server configured
on the DHCP page (which defaults to the router
itself).
If you need DNS Director to redirect to an IP
configured in your DHCP settings, use a Custom DNS
entry in DNS Director. This makes it more consistant
with what the name implies, and was also necessary
for improved Guest Network support.

---

I also tried the new suggestion from the changelog, which recommends setting 'Global Redirection = User Defined 1' to redirect the IP instead of using the DHCP → DNS Server 1 setting. This doesn’t work either. The device still shows the router (192.168.2.1) as the assigned DNS, and no traffic is passing through the AdGuard Home server anymore.

I'm trying to understand what exactly changed because it doesn't seem like anything has. I also tried the new suggested method, but it keeps reverting to 192.168.2.1 (my router) and ignoring what's in the User Defined 1 field.

 

[dave14305]

The device won’t detect if DNS Director is intercepting DNS or not. That’s why the DNS you see on the device doesn’t change. The router’s firewall is intercepting the DNS requests and directing them as configured without the client’s knowledge.

 

[bennor]

I also tried the new suggestion from the changelog, which recommends setting 'Global Redirection = User Defined 1' to redirect the IP instead of using the DHCP → DNS Server 1 setting. This doesn’t work either. The device still shows the router (192.168.2.1) as the assigned DNS, and no traffic is passing through the AdGuard Home server anymore.

There are two different things at work here.

First is what DNS server the client is assigned when it is configured to obtain it's IP address and DNS server from the router's DHCP server and that DHCP server's DNS settings. If you configure the client to use the router as it's DNS server, then that's the value the client displays for it's DNS server. If you enter a DNS server into the router's DHCP server DNS server section, then that's the value the client displays as it's DNS server.

Second is what the router does when it receives a DNS request from a client when DNS Director is enabled and intercepting DNS requests on the router. Generally the client doesn't know about DNS Director or that it's intercepting requests. The client won't show what DNS server one has configured DNS Director to use. The router is translating the DNS request.

Edit to add: If you have configured DNS Director to use the AdGuard Home Server (192.168.2.2) then check AdGuard Home Server's logs (or settings) to see if it indicates the clients are sending DNS requests through it.