The client does a fallback if one dns doesn’t answer. That’s why dns ad blockers fail if 8.8.8.8 or some other dns is added as a secondary :)
The client does a fallback if one dns doesn’t answer. That’s why dns ad blockers fail if 8.8.8.8 or some other dns is added as a secondary :)
Dave@lemmy.nz 11 months ago
Hmm I’ve definitely see clients just say no when the first fails. How do they tell the router to try the other one? Does the router send both DNS servers to the client or does the client request a lookup from the router? Maybe my router sucks.
SciPiTie@iusearchlinux.fyi 11 months ago
The router is not directly involved in a dns query except, we’ll, the routing if it’s an non local IP. The DNS ip addresses is propagated either via dhcp together with the clients or directly configured in the client. That said: most routers serve as dhcp server at the same time. Perhaps your router is configured to always provide your ISPs DNS as primary.
How the client handles the decision which to query I honestly don’t know and I guess that’s why you and I made different experiences!
Dave@lemmy.nz 11 months ago
My router is configured with both primary and secondary DNS pointing to my pihole, but in the past I’ve had one valid and one invalid one and the DNS lookup would fail approx half the time. It was a few years ago (but not that many). I wonder what was up with that.