pros and cons for the two common DNS setups for a local adblocker - adguard home

[Tech9]

I don't have any of the setups running at the moment (my Asus router is for experiments only), but from memory what was coming from the router in both cases was only WAN monitoring queries to Microsoft server and occasionally TrendMicro. Everything else was correctly recognized by client IP and I had hostnames set for easier client identification. I had my separate device configuration posted somewhere in AGH related threads. Not sure if there is a difference in AGH run in a container or whatever it uses there on your NAS. May have some specifics.

 

[jtp10181]

but with DNS Director On (and yes, No redirection on the separate device), it will still show the most active client as the Router itself.

That means those requests were sent to the router and would have bypassed your AGH setup without the DNS Director enabled. DNS Director redirected it to the AGH from the router so it looks like the request came from the router. Are you sure you are not advertising the router IP along with the SGH IP in the DHCP? If you have IPv6 enabled you have to set a DNS for that also or the router will advert itself!

Also some devices will ignore the DHCP if stuff is getting blocked and just try using some hard coded DNS, which is where the director comes in.

(1) I am setting this via a script to force it as an IPV4 mapping, but it can be set directly here
192.168.1.8 is the AGH server.

 

[pjd50]

I don't have any of the setups running at the moment (my Asus router is for experiments only), but from memory what was coming from the router in both cases was only WAN monitoring queries to Microsoft server and occasionally TrendMicro. Everything else was correctly recognized by client IP and I had hostnames set for easier client identification. I had my separate device configuration posted somewhere in AGH related threads. Not sure if there is a difference in AGH run in a container or whatever it uses there on your NAS. May have some specifics.

Yeah, it's AGH running on Portainer on Synology NAS. Perhaps I need to adjust the set-up. Any tips on where I can find the right information? I followed all the steps here (and doesn't mention anything about DNS Director etc.): https://mariushosting.com/synology-install-adguard-with-portainer/

 

[pjd50]

That means those requests were sent to the router and would have bypassed your AGH setup without the DNS Director enabled. DNS Director redirected it to the AGH from the router so it looks like the request came from the router. Are you sure you are not advertising the router IP along with the SGH IP in the DHCP? If you have IPv6 enabled you have to set a DNS for that also or the router will advert itself!

(1) I am setting this via a script to force it as an IPV4 mapping, but it can be set directly here
192.168.1.8 is the AGH server.
View attachment 55283

View attachment 55284

Thank you for the clarification! That makes sense actually - I was thinking I saw more ads "leaking" through on some of my devices... I have now re-enables DNS Director...

No, I don't have IPv6 enabled...

 

[pjd50]

That means those requests were sent to the router and would have bypassed your AGH setup without the DNS Director enabled. DNS Director redirected it to the AGH from the router so it looks like the request came from the router. Are you sure you are not advertising the router IP along with the SGH IP in the DHCP? If you have IPv6 enabled you have to set a DNS for that also or the router will advert itself!

Also some devices will ignore the DHCP if stuff is getting blocked and just try using some hard coded DNS, which is where the director comes in.

(1) I am setting this via a script to force it as an IPV4 mapping, but it can be set directly here
192.168.1.8 is the AGH server.
View attachment 55283

View attachment 55284

And Yes, I'm positive I'm not advertising:

So what's the way I can show the "offending" devices that are trying to bypass my AGH device and sending DNS requests straight to the router?!

 

[Tech9]

The queries may give you clues. Reboot the suspected devices and they will get your 192.168.75.100 as DNS from DHCP.