When "using OpenDNS" changes to 'No" - notify me! Make it obvious.

Follow

chris.blyseth

April 07, 2014 11:35

Verizon FIOS recently switched me over to to the latest ''WAN' port (Ethernet). I had no idea this happened. This new connection set the DNS entries to the default on that connection. The old connection (PPOE) with my OpenDNS entries was disabled.

Please make the OpenDNS pop-up flash red and send me an e-mail when it appears I've stopped using OpenDNS. Make the notifications each an option with email defaulted to 'enabled'.

 

Thanks

0

• 

  rotblitz April 07, 2014 13:17

  OpenDNS cannot know when you don't use it, because you don't use it then, and there is no way to determine if this is by intention or not.

  The OpenDNS Updater knows and alerts you accordingly already, via red pop-up, not via e-mail.  In case you haven't it installed yet, do so now.

  0

  Comment actions Permalink
• 

  dgkanter July 07, 2015 00:58

  I, too, went for a very long time not realizing I wasn't I wasn't using OpenDNS 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 using Open DNS.

  If OpenDNS doesn't know the status until a "Show Status" is invoked, then is there some reason 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. (I'd see that user-enabled process being along the lines of where an app periodically checks for software updates.)

  Having the user being left "in the dark" about no longer using the OpenDNS servers is not a trivial operational matter.

  Thanks for listening.

  0

  Comment actions Permalink
• 

  rotblitz July 07, 2015 19:09

  "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".

  0

  Comment actions Permalink

Please sign in to leave a comment.