glnzglnz
commented
5 years ago UPDATE: So I experimented and confirmed that there IS a relationship between dnscrypt-proxy and the Warning above. I first "Removed Service" using Simple DNSCrypt and rebooted, and the Warning did NOT recur. Then I re-enabled the service and rebooted, and the Warning occurred again on this last reboot. Actually, I am getting two Warnings that occur only when dnscrypt-proxy runs at start up:
- "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." Is there anything I can do in the dnscrypt-proxy settings that will let _ldap._tcp.dc._msdcs.fios-router.home and wpad (whatever that is) get the needed DNS responses and do what they want to do? Thanks.
BallonLac
I love Simple DNSCrypt. However, on every reboot of my Win 10 Pro 64-bit PC, I get this Warning 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." It mentions fios-router.home, which is my Quantum G1100 router for FIOS 1Gbps. So, is it possible that dnscrypt-proxy and the DNS server at 127.0.0.1 are missing a needed link or DNS entry to reach _ldap._tcp.dc._msdcs.fios-router.home inside my Quantum G1100 router?
(By the way, when I want to access that router, I go to 192.168.1.1, hit "Proceed", enter the password, and I'm in. And, recently, Verizon updated its firmware to require the acceptance of a self-signed certificate to access the router that way, which I accepted. Yes, I can access the router that way - I just tried again.) What should I do about the Warning on every reboot? Thanks.