If what you said was true, my secondary Pi-hole wouldn’t have to respond to any queries. It it in fact gets quite a lot of them. As the other poster has said, it is about 80/20 for 1st and 2nd pihole. Sometimes the ratios are different, depending on the time of day (don’t ask me why….).
Comment on When Pi-hole is down?
Bizarroland@kbin.social 4 months agoProof?
I read 15 different sites about DNS and not a one of them claimed anything like this. They universally all stated that your network attached devices would use the 1st one unless it didn't respond and only use the 2nd one if the 1st one did not.
So once again, I ask "Can you send me some more information on this" and not just claim it without any backup information?
I apologize if I am coming off rude, just my BS meter is getting close to the red zone and I would really appreciate some reliable evidence.
B0rax@feddit.de 4 months ago
adam@kbin.pieho.me 4 months ago
On the left is the DNS server that DHCP sets first. On the right is one it sets second.
This is a mixed machine network (Windows, MacOS, iOS, Android etc).
My clients will mostly pick option number one, but as you can see it's not a guarantee at all.
Attachment: media.kbin.pieho.me ↗
EncryptKeeper@lemmy.world 4 months ago
The best proof would be to just try it yourself and see what happens. Load up Wireshark, make a query, and look at your traffic. Because the problem is there isn’t a single technical article I can point you to that details exactly how DNS resolution works on every device running any given operating system. “Network attached devices” could be anything and so you can’t be certain exactly how each device will operate.
I’ll give you that in the case of Windows devices specifically, Microsoft isn’t good at keeping documentation up to date, and on older version of windows it used to work the way you describe. It would send the request to your first DNS server, wait one second for a response, and only if it didn’t get one would it move on to your next one. However in Windows 10 today if I edit my configuration so that I use a local DNS server located at 192.168.69.210 as my “Preferred” DNS server and 1.1.1.1 as my “Alternate” DNS server look what happens:
Image
It sends the same request out to both without waiting and the response from Cloudflare actually comes in before the one from my local DNS server. So if this were a request for a blocked domain, the client would accept the response from Cloudflare because it was received first and so the request wouldn’t be blocked.