Windows 10: DNS Name resolution for “_ldap._tcp.dc._msdcs.fios-router.home” & “wpad” BLOCKED by...

This first post is a bit long because I've added some updates, but it also has some good stuff for you, so please bear with me. HOWEVER, please DO NOT post any stock answer. This query will NOT be fixed by any kind of automatic answer. PLEASE ABSORB THE DETAILS.


On every reboot of my Win 10 Pro 64-bit (version 1803) 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."
and
"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:
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. My only "resolver" is cloudflare's newish 1.1.1.1 service.

First, there's a superb article on ars techinca that explains everything about dnscrypt-proxy and cloudflare's secure 1.1.1.1 DNS lookup service 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.


UPDATE -

As to the Event 1014 Warning that "Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded.":

I've done some more digging, and the dnscrypt-proxy service I am using to encrypt my DNS lookups and send them only to cloudflare's new 1.1.1.1 has a Forwarding feature, maybe especially for cases like this.

See < THIS PAGE ON GITHUB >


MORE Update - trying to follow the wiki link about Forwarding -

1. I put forwarding-rules.txt into the same folder as dnscrypt-proxy.toml.
2. I added the line forwarding_rules = "forwarding-rules.txt" (using double-quotes not single quotes) to dnscrypt-proxy.toml right after the line cache_neg_ttl = 60
3. The only line I put in forwarding-rules.txt is fios-router.home 192.168.1.1

Is that correct?


RESULTS - The above didn't work, and on reboots I continue to get the Event 1014 Warning "Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded."


What next?

:)

 

Fresh Install Win10 "Name resolution for the name wpad timed out" DNS




So I should switch from auto to manual using the opendns you gave?

 

Name resolution for the name wpad timed out after none of the configured DNS servers responded.

Hello

I get the warning 'Name resolution for the name wpad timed out after none of the configured DNS servers responded.' in event viewer whenever my Wifi drops out - which is every 10-30 minutes. It's a Lenovo Thinkpad T440p running Windows 10 pro.

I've already changed the Wifi card (Intel 7260NGW on the m.2 slot), installed different driver versions, reinstalled Win10. This only happens on Wifi, it's fine on LAN with the same router. This seems to be a software problem which only occurs on Windows.
Wifi works with Linux, but I need it to work on Windows as I work with lots of Windows programs.

Any ideas please?

 

DNS problems with router

A couple suggestions I have for you:

Update the firmware on the router. Maybe it's getting into a badstate, and a firmware update might fix it. Or if you're comfortable with it, install a custom firmware like dd-wrt. Just make sure its supported on your router first.

Change your DNS to: 8.8.8.8, 4.2.2.1. Might help.

If none of these work, maybe statically set your DNS on your PS3/PC to the IPs you listed, taking the router out of the lookup procedure.

Last option, is look for a new router.