AGH DNS Director problem

[FourthandShort]

The behavior of Router mode changed in 3006.102.4, so old advice is outdated.

This is the best scenario. Most clients will talk directly to AGH and appear properly in the logs.

I home I am not becoming a pest, but I wanted to follow up on a last item.

As part of the previous instructions, an entry was made to the Route to redirect both 8.8.8.8 and 8.8.4.4 to 192.168.50.1 (router). In the past with DNS Director we were routing everything to the router. As now we are routing the DNS through the LAN to the AGH server, should I update the route to point to the AGH server instead of the router?

 

[dave14305]

As part of the previous instructions, an entry was made to the Route to redirect both 8.8.8.8 and 8.8.4.4 to 192.168.50.1 (router)

I cannot think of a good reason to do this if you’re already using DNS Director.

 

[FourthandShort]

I cannot think of a good reason to do this if you’re already using DNS Director.

I have a couple Roku's in the house and according to a couple posts it was recommended here: Link

To block hard coded DNS servers in IoT and other devices that may bypass the Pi-Hole, one can try to do so with the following steps.

On the LAN > Route > Basic Config set "Enable static routes" to Yes.​

Input the hard coded DNS server into the "Network Host/IP field.​

Input "255.255.255.255" into the "Netmask" field.​

Input or select the router's IP address in the "Gateway" drop down box.​

Set "Metric" field to "2".​

Select "LAN" from the "Interface" dropdown box.​

Click the Plus icon to add the entry.​

Repeat as needed to add other hard coded DNS servers you want to block.​

Click the Apply button when finished.​

Thoughts? Needed? Not? If not i can remove it. Otherwise, should it point to the router or the AGH? Thanks again.

 

[bennor]

Thoughts? Needed? Not? If not i can remove it. Otherwise, should it point to the router or the AGH? Thanks again.

@FourthandShort, you have quoted a comment i made in an entirely different discussion, in response to likely an entirely different question (PiHole DNS). As such it might not be relevant here or with AGH. What is your use case or reason for wanting to use the Routing tab to route 8.8.8.8 and 8.8.4.4? Are you trying to route those two DNS addresses to AGH?

PS: Those steps that I described are a method of blocking a public DNS. Typically it causes a client not to be able to reach the indicated public DNS server. That process for blocking Google DNS servers is explained elsewhere. For example:

https://support.strongvpn.com/hc/en-us/articles/360043339733-Blocking-Public-DNS-on-an-Asus-Router

How to Block Google DNS on Asus Router - Unlocator Support

Make sure your DNS is set to the Unlocator DNS 185.37.37.37 and 185.37.39.39. Follow the Asus guide here https://support.unlocator.com/customer/portal/articles/

support.unlocator.com

 

[FourthandShort]

@FourthandShort, you have quoted a comment i made in an entirely different discussion, in response to likely an entirely different question. As such it might not be relevant here or with AGH. What is your use case or reason for wanting to use the Routing tab to route 8.8.8.8 and 8.8.4.4? Are you trying to route those two DNS addresses to AGH?

PS: Those steps that I described are a method of blocking a public DNS. Typically it causes a client not to be able to reach the indicated public DNS server. That process for blocking Google DNS servers is explained elsewhere. For example:

https://support.strongvpn.com/hc/en-us/articles/360043339733-Blocking-Public-DNS-on-an-Asus-Router

How to Block Google DNS on Asus Router - Unlocator Support

Make sure your DNS is set to the Unlocator DNS 185.37.37.37 and 185.37.39.39. Follow the Asus guide here https://support.unlocator.com/customer/portal/articles/

support.unlocator.com

Apologies for quoting it out of the blue.

You have a couple really well detailed posts about getting AGH working which I was trying to follow the past few days, however it appears with a new firmware, some of the information may need to be updated. For example in your post, you reference adding an entry in DNS Director to set the Global Redirection back to the router and my understanding is if I have a AGH server running on a pc (192.168.50.184 in my case), to force all traffic to use that DNS server, I need to instead set the global redirection to custom user 1 where I add 192.168.50.184.

I was curious if the route was still needed to block the 8.8.8.8, and if so, should I point the route using your instructions to the router IP or the AGH IP? Any help would be great.

 

[bennor]

You have a couple really well detailed posts about getting AGH working which I was trying to follow the past few days, however it appears with a new firmware, some of the information may need to be updated.

Please note I have never used AGH. I use Pi-Hole and Unbound running on a Raspberry PI for my network client DNS servers. Pi-Hole may require different router settings than those required by AGH. That post of mine you quoted was from 2021, well before the release of the 3006.102.4 (10-May-2025) firmware where RMerlin made a change in how DNS Director operates (see the change log).

- 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.

There was mention of this change in the 3006.102.4 beta discussion by @dave14305 and how it may require Pi-Hole users to adjust their DNS Director settings. See this post and several replies that stemmed from it, including this post I made in reply to someone else.

 

[FourthandShort]

Please note I have never used AGH. I use Pi-Hole and Unbound running on a Raspberry PI for my network client DNS servers. Pi-Hole may require different router settings than those required by AGH. That post of mine you quoted was from 2021, well before the release of the 3006.102.4 (10-May-2025) firmware where RMerlin made a change in how DNS Director operates (see the change log).

There was mention of this change in the 3006.102.4 beta discussion by @dave14305 and how it may require Pi-Hole users to adjust their DNS Director settings. See this post and several replies that stemmed from it, including this post I made in reply to someone else.

Yep, this is great and thank you, your follow up post is perfect and apologies I missed it.

If i end up pointing the Global Redirection from "Router" to the AGH/Pihole, would I also need to update the Static Routes or would those still need to point to the router? I think that is where my confusion sits now unfortunately. Appreciate any feedback you might have.