I have been running with Adguard and Unbound on the GL-X2000 for a week or two. I made a rule in the firewall as instructed here
config rule
option dest 'wan'
option dest_port '53 853 5353'
option enabled '1'
option family 'any'
option name 'Block-Public-DNS'
option proto 'tcpudp'
option src 'lan'
option target 'REJECT'
Works very well to force all DNS requests into Adguard and make every device exclusively use the DNS running on the device (unbound).
But I have realized that perhaps it is better to run Adguard and Unbound on a seperate server, and let the router focus on traffic
On this new server, everything works nice, except for the rule to force exclusive DNS. I am not seeing Chromecast anymore, for example. I’m sure it has hardcoded DNS.
So I was wondering if it was possible to make this same thing work, in some other way. I feel it might be doable, but I cannot figure out how.
Have found one way of doing it, that requires me to make a port forwarding rule for the IPs that I want to force. If I make a gereral rule like this, I am unable to browse the web.
I am using the DNS for the AGH server in glinet menu.
Forwarding all DNS is a rule I can setup in LUCi? Will look into that. And blocking all other on AGH on my server, ok will try. Currently only the Unbound server is listed as DNS in AGH.
Thanks a lot for answering and having patience with my lacking ability to make this work for all devices.
I tried everything in your link to see if it would work, and it did work for my TP device. It is now forced to go via Adguard Home on my Proxmox server.
Unfortunatly my two Chromecast devices just refuses to play ball with these general rules. I have no idea why. Maybe I am doing something wrong (very likely), or perhaps I should factory reset the router.
But the specific rules work, so that’s the way forward for me for now.
There are also ip block lists, my suggestion is to use something like banip it has a way to block a big list on DoH ips, there is still a loophole available once ip connectivity with DoH fails it falls back to traditional dns in where dns hijacking works again.
Currently that is how I work around the issue, besides blackholing 8.8.8.8 entirely.