search

bitbeans / SimpleDnsCrypt

A simple management tool for dnscrypt-proxy
https://simplednscrypt.org
MIT License
2.29k stars 233 forks source link

Name resolution for "_ldap._tcp.dc._msdcs.fios-router.home" & "wpad" BLOCKED by dnscrypt-proxy! How to fix? #410

Open glnzglnz opened 5 years ago

glnzglnz commented 5 years ago

Love Simple DNSCrypt 64-bit, but maybe there's a problem. I have Simple DNSCrypt 0.6.4 (64-bit) pushing dnscrypt-proxy 2.0.22. On every reboot of Win 10 Pro 64-bit version 1803 (home PC wired to 1Gbps FIOS gateway), I get two or three Warnings in Event Viewer with "Event 1014 DNS Client Events":

One suggested fix is to turn off "Automatically detect settings" in Proxy in Network & Internet in Control Panel. But would that interfere with dnscrypt-proxy?? Or is there a way to add needed info to "the configured DNS Servers"?

What do you suggest? Thanks.

glnzglnz commented 5 years ago

UPDATE: So I experimented and confirmed that there IS a relationship between dnscrypt-proxy and the Warnings above. I first "Removed Service" using Simple DNSCrypt and rebooted, and the Warnings did NOT recur. Then I re-enabled the service and rebooted, and the Warnings occurred again on this last reboot.

And here again are the two Warnings that occur only when dnscrypt-proxy runs at start up:

  1. "Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded." and
  2. "Name resolution for the name wpad timed out after none of the configured DNS servers responded."

Both are Event 1014, DNS Client Events. And, by the way, fios-router.home must be my Quantum G1100 modem-router supplied by Verizon for my 1Gbps FIOS service, which has been pretty darned good.

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.

glnzglnz commented 5 years ago

Update - just tried nslookup. It says "Domain: fios-router.home" but then says it can't find that domain. Here's a link to a screenshot showing that - gif and pdf: < LINK > Mean anything?

glnzglnz commented 5 years ago

TWO THINGS - and the first is more important:

FIRST: I did some digging, and the wiki is giving me a clue for ONE of my Event 1014 Warnings, but I need your help to implement. See the wiki about Forwarding at https://github.com/jedisct1/dnscrypt-proxy/wiki/Forwarding But how Should i set this up for the Event 1014 Warning about _ldap._tcp.dc._msdcs.fios-router.home ?
Should I just point it to 192.168.1.1 (which is the router)? Don't I need a suffix, maybe for a port? How would I find that?

SECOND: The above two Event 1014 Warnings continue to occur on every reboot. This morning, I have a new one, appearing only once so far:

Yes, my Win 10 Pro 64-bit has OneDrive, which starts at startup, and so maybe there's a connection to this static2.sharepointonline.com that I'd never heard of before. And, today, trying to find a fix for other issues, I "reset" OneDrive although afterwards it seems to be the same as it always was. On the other hand, Simple DNSCrypt / dnscrypt-proxy should be able to find the right DNS lookup for anything, no? This new Warning is only once so maybe meaningless, but who knows - maybe there's a small limitation in the Simple DNSCrypt / dnscrypt-proxy setup that needs to be addressed? Thoughts? Thanks.

glnzglnz commented 5 years ago

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?

glnzglnz commented 4 years ago

Almost a year later, and I still get

"Name resolution for the name wpad timed out after none of the configured DNS servers responded." "Name resolution for the name _ldap._tcp.dc._msdcs.fios-router.home. timed out after none of the configured DNS servers responded."

on reboots. But I love Simple DNSCrypt!

glnzglnz commented 4 years ago

I am beginning to understand a little better.

As to the the ldap._tcp.dc._msdcs event viewer error, my setup is WORKGROUP, not domain. I confirm this by going to Control Panel\All Control Panel Items\System, where "Domain:" does NOT appear but "Workgroup: WORKGROUP" does appear. (I am at home, and I would be astonished if any of my devices thought it was on a domain.)

Can it be that my reboot event viewer error code is because my Win 10 Pro 64-bit is default-designed to look for a domain, and this event viewer error pops up because in fact there is no domain? (But why hasn't anyone else complained?)

As to Web Proxy Auto-Discovery (WPAD) Protocol, since I am running dnscrypt-proxy (set up via Simple DNSCrypt), that may itself be some type of proxy-based service (for its limited purpose of DNA lookups), and so maybe WPAD is frustrated because there is no other proxy for what happens after?

Could it be that both these event viewer errors show because the dnscrypt-proxy service doesn't start fast enough?

What do you think?

Thanks.