Both OpenDNS Updater and DNSCrypt Should Advise of a Mutually-Exclusive Conflict
After an extended dialog with Mahshad Sarband (OpenDNS) under ticket #158595, I ultimately learned that the reason I couldn't use the DNS Servers was because I had activated DNSCrypt and, unbeknownst to me, that removed the 208.67.222.222 & 208.67.220.220 entries I had made for the DNS Servers and substituted 127.0.0.54--which OpenDNS Updater's "Show Status" then indicates "No" to me not using Open DNS. (I've separately commented on the thread about not being advised by OpenDNS Updater when the using-OpenDNS status had switched to "No", but the users don't know until they do a "Show Status" under OpenDNS Updater as the menubar icon remains the same whether the status is "Yes" or "No".)
I recommend code be added to both OpenDNS Updater and DNSCrypt so a user is advised, up-front, by a notification/alert when they install and activate both DNSCrypt and OpenDNS Updater that the two conflict with each other, DNSCrypt "wins", and the user has no means to mitigate the conflict.
Thanks for listening.
-
Repeating my answer from https://support.opendns.com/entries/31221864 :
"removed the 208.67.222.222 & 208.67.220.220 entries I had made for the DNS Servers and substituted 127.0.0.54"
Sure, this is intentional and does not stop you using OpenDNS. This 127.0.0.X is the address the dnscrypt-proxy listens on, but it still forwards your DNS queries to OpenDNS, 208.67.220.220. Even more, you seem to run an old preview version of DNSCrypt, because the dnscrypt-proxy doesn't change your network settings at all. You must change it yourself.
See http://dnscrypt.org/"which OpenDNS Updater's "Show Status" then indicates "No" to using Open DNS."
That must be a different issue. No matter if you use dnscrypt-proxy or not, the Updater sends DNS query probes to myip.opendns.com. If it shows Using OpenDNS = No, then it could not query this domain.
"why it can't have a user-enabled option to periodically invoke a "Show Status and if it is "No", then generate a notification and/or change the OpenDNS Updater's to reflect a "No" status (perhaps a red exclamation symbol."
Exactly this is the case with the Updater already. And if you use the (current) dnscrypt-proxy and aren't using OpenDNS (or another DNS service you have chosen), then you have no DNS at all, looking like no internet connection. This should be enough "notification".
-
Also, you should be aware that the DNSCrypt client isn't an OpenDNS supplied program. You're wrong in this forum.
Here you go: http://dnscrypt.org/
Please sign in to leave a comment.
Comments
2 comments