solehad
New Around Here
Hi,
Sorry if this is in the wrong forum. I've got an issue with DNSFilter on my RT-AC68u running merlin 386.7_2 (but this issue also affected previous versions). I'm not sure if this is a bug or if I don't understand something about DNSFilter (quite possibly the latter).
My router is at 10.0.0.1/24 and a pihole is at 10.0.0.3. The router's DHCP server is configured to provide 10.0.0.3 and 10.0.0.1 as DNS servers (in that order). DNSFilter is enabled, with the global filter mode set to Router and the device at 10.0.0.3 configured to allow no filtering.
When 10.0.0.3 is up and running everything works perfectly. From DHCP clients on the network I can resolve names against 10.0.0.3, and if I resolve against 10.0.0.1 I can see in the pihole logs that the router is forwarding the resolution request to pihole.
The problem starts if pihole goes offline. When this happens, DNS resolution breaks entirely. I can't resolve addresses against 10.0.0.1 because, I assume, the router is trying to forward requests to pihole at 10.0.0.3 which is offline.
However, if I configure the router as the first DNS entry under DHCP server settings, DNS resolution works when the pihole is offline.
Based on my configuration and the description of how DNSFilter works, I would not expect any issues with my configuration, and I would expect the router to be able to resolve DNS using an upstream forwarder when the pihole is offline. Or, to put another way, I would not expect DNSFilter to redirect the resolution requests for something (in this case itself) which is configured as the second DNS server in DHCP server settings.
Any thoughts? Thanks!
Sorry if this is in the wrong forum. I've got an issue with DNSFilter on my RT-AC68u running merlin 386.7_2 (but this issue also affected previous versions). I'm not sure if this is a bug or if I don't understand something about DNSFilter (quite possibly the latter).
My router is at 10.0.0.1/24 and a pihole is at 10.0.0.3. The router's DHCP server is configured to provide 10.0.0.3 and 10.0.0.1 as DNS servers (in that order). DNSFilter is enabled, with the global filter mode set to Router and the device at 10.0.0.3 configured to allow no filtering.
When 10.0.0.3 is up and running everything works perfectly. From DHCP clients on the network I can resolve names against 10.0.0.3, and if I resolve against 10.0.0.1 I can see in the pihole logs that the router is forwarding the resolution request to pihole.
The problem starts if pihole goes offline. When this happens, DNS resolution breaks entirely. I can't resolve addresses against 10.0.0.1 because, I assume, the router is trying to forward requests to pihole at 10.0.0.3 which is offline.
However, if I configure the router as the first DNS entry under DHCP server settings, DNS resolution works when the pihole is offline.
Based on my configuration and the description of how DNSFilter works, I would not expect any issues with my configuration, and I would expect the router to be able to resolve DNS using an upstream forwarder when the pihole is offline. Or, to put another way, I would not expect DNSFilter to redirect the resolution requests for something (in this case itself) which is configured as the second DNS server in DHCP server settings.
Any thoughts? Thanks!