JoeTheDownloader
Occasional Visitor
This is more a "what's going on" than an actual problem, but I learn a lot this way so here goes and thanks in advance for any help:
Scenario:
The pi-hole receives frequent DNS requests for www.google.com (A and AAAA records) and occasional other subdomains of google from the router itself.
I don't understand why the router is generating this traffic, or if perhaps it is forwarding it on behalf of another device. I don't understand why it is forwarding it to the pi-hole recursively, rather than looking it up using the DNS configured on the WAN.
Weird!
Thanks again for reading, if indeed you still are.
Scenario:
- RT-AC68U, Merlin 386.9, henceforth "the router"
- Everything is working just fine
- The router is the D/G for the local LAN only, a flat /24 network
- DHCP is on the router only - it hands out DHCP leases with the DNS pointing to a pi-hole (which is itself not a DHCP server)
- DNSDirector is also configured on the router to push any stubborn devices towards the pi-hole
- The router's own DNS is pointed at Google 8.8.8.8/8.8.4.4 with DNSSEC enabled, DNS Rebind protection on and Prevent client auto DoH set to auto. DNS priv protocol is set to none.
- The router has a DNSDirector exemption allowing the pi-hole to be exempt from filtering
- The pi-hole's own DNS is set to be the router, since I need to resolve internal things too
- Forward local domain queries to upstream DNS is enabled since I use my domain name internally but also externally to give split horizon DNS for convenience
The pi-hole receives frequent DNS requests for www.google.com (A and AAAA records) and occasional other subdomains of google from the router itself.
I don't understand why the router is generating this traffic, or if perhaps it is forwarding it on behalf of another device. I don't understand why it is forwarding it to the pi-hole recursively, rather than looking it up using the DNS configured on the WAN.
Weird!
Thanks again for reading, if indeed you still are.