Blocking Secondary DNS? 127.0.0.1?
I know the DNS secondary is for redundancy sake in case one fails and removing that might leave me not able to connect if the single one fails and I am fine with that.
I added 127.0.0.1 as one of the DNS and I noticed that the system queries that like 9 times. I am just wondering is if a safe practice? or should I be utilizing another method to eliminate the secondary dns.
EDIT: was able to achieve by changing it in the registry. WINDOWS 10./
Posted Sep 11, 2021, 12:05 AM UTC · edited
05
Just set one, then?
I believe most will keep trying whatever IPs are there, to check whether it's up and it can query, which it uses for its algorithms of which to prefer.
OP should specify their operating system but yes, just set one would be my answer as well.
My setup didnt allow for only 1 dns, so I had to add that loopback one of 127.x.x.x but like I said it added latency with the numerous attempts so I had the bright idea of null with 0.0.0.0 but it wouldnt allow me to place that as the dns so instead I figured out how to edit it to 0.0.0.0 through the registry and now all is fine. My dns queries for forced to go to the only dns I have chose.
What setup is that? Sounds odd.
Another thing you could do is add the same IP twice if for some strange reason you must enter two, but most contexts should accept only one.
its through a firewall I use that pulls the dns form the system but the if system only has 1 dns it pulls the other dns from the router which I didnt want so had to fill in both dns and it never came to my mind to put the same dns twice lol.