On every reboot of my Win 10 Pro 64-bit PC, I get two Warnings in Event Viewer:
"Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded."
"Name resolution for the name wpad timed out after none of the configured DNS servers responded."
Both are Event 1014, DNS Client Events.
The first Warning’s reference to “fios-router.home” must be to my Quantum G1100 modem-router that was supplied by Verizon for my FIOS 1Gbps service. Also, the DNS name resolution is probably needed for proper functioning of the Quantum G1100’s “Active Directory”. See item #4 at this link: -THIS LINK ON MSDN-
But I’m not a tech and don’t know how to start fixing this.
EDIT - More info - and I certainly need your help:
By experimenting, I have determined that these Warnings occur when I have the service dnscrypt-proxy running at startup. It’s a great service that encrypts DNS lookup requests so that nobody - not Verizon and not Google and not man-in-the-middle bad guys – can see where I am trying to go. By the way, I have always set my Simple DNSCrypt to use ONLY cloudflare’s 126.96.36.199 and 188.8.131.52 as its resolvers.
First, there’s a superb article on ars techinca that explains everything about cloudflare’s 184.108.40.206 and dnscrypt-proxy in great detail: How to keep your ISP’s nose out of your browser history with encrypted DNS
Second , you can download and get technical info about Simple DNSCrypt - which helps you install and configure dnscrypt-proxy on a Win machine - from github at github-bitbeans-SimpleDnsCrypt
Third , what should I do to continue using dnscrypt-proxy but let “_ldap._tcp.dc._msdcs.fios-router.home” and “wpad” get the needed DNS/name resolution and so not generate the Warnings I describe above? ◄ This is the important question.