OpenDNS timing out and doesn't work?

Follow

content2be

September 20, 2013 23:19

I have not been able to get OpenDNS web content protection to work for me for a while.  I've been a subscriber since 2011, but in the last couple of months, it just stopped working.  I have very little computer knowledge, but my router is a Belkin. I emptied my browser cache and did ipconfig/flushdns The DNS  settings on my router are set to 208.67.220.220 and 208.7.222.222.  When I visit the welcome DNS page, I get "Your Internet is faster, safer, and smarter because you're using OpenDNS." What am I doing wrong? 

This is the result of debug command:

> nslookup-type=txt debug.opendns.com
Server: debug.opendns.com.Belkin
Address: 67.215.65.132

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to debug.opendns.com timed-out
>

0

• 

  maintenance September 21, 2013 03:32

  You see the IP address that was returned? that is for hit-nxdomain.opendns.com because there is no such thing as debug.opendns.com.Belkin

  0

  Comment actions Permalink
• 

  maintenance September 21, 2013 03:35

  i.e., you need the required trailing dot to make an FQDN as demanded by nslookup, or the DNS suffix gets appended. (Which you likely do not need,either.)

  0

  Comment actions Permalink
• 

  content2be September 21, 2013 15:03

  When I do the command with a period at the end, I get this.

  > nslookup-type=txt debug.opendns.com.
  *** Can't find address for server debug.opendns.com.: Non-existent domain
  >

   

  0

  Comment actions Permalink
• 

  rotblitz September 21, 2013 15:36

  "> nslookup-type=txt debug.opendns.com
  Server: debug.opendns.com.Belkin
  Address: 67.215.65.132"

  Oops, you first entered nslookup to go into the nslookup prompt, and then you entered the whole command again.  That was absolutely wrong.  You must enter the whole command in a cmd (command prompt) window, not in an nslookup prompt.

  Start > Run > cmd
  (Then in the command prompt window, with trailing dot:)
  nslookup -type=txt debug.opendns.com.

  0

  Comment actions Permalink
• 

  content2be September 21, 2013 16:04

  What am I doing wrong?  I am so sorry, but I am very ignorant.  I did open a ticket yesterday, but I imagine it will be at least Monday before I hear from anyone.

  Here is what I got after I did it as you instructed above.

  Microsoft Windows [Version 6.1.7601]
  Copyright (c) 2009 Microsoft Corporation. All rights reserved.

  C:\Users\Deena>nslookup-type=txt debug.opendns.com.
  'nslookup-type' is not recognized as an internal or external command,
  operable program or batch file.

  C:\Users\Deena>

   

  0

  Comment actions Permalink
• 

  content2be September 21, 2013 16:24

  Just realized there was a space after lookup! SORRY.  Tried it again and this is what I got.

  C:\Users\Deena>nslookup -type=txt debug.opendns.com.
  1.2.168.192.in-addr.arpa
  primary name server = localhost
  responsible mail addr = nobody.invalid
  serial = 1
  refresh = 600 (10 mins)
  retry = 1200 (20 mins)
  expire = 604800 (7 days)
  default TTL = 10800 (3 hours)
  Server: UnKnown
  Address: 192.168.2.1

  Non-authoritative answer:
  debug.opendns.com text =

  "server 5.ash"
  debug.opendns.com text =

  "flags 20 0 2f4 800000000000000"
  debug.opendns.com text =

  "id 0"
  debug.opendns.com text =

  "source 184.56.153.171:9872"

  C:\Users\Deena>

  0

  Comment actions Permalink
• 

  rotblitz September 21, 2013 23:03

  Brilliant, nearly everything is fine regarding your DNS queries. It proves that you have the OpenDNS resolver addresses configured on the router at 192.168.2.1, and that you are using the OpenDNS location in Ashdown (WDC). You are located around Brunswick, Ohio.

  Back to your original problem:
  "I have not been able to get OpenDNS web content protection to work for me for a while."

  Yes, your IP address 184.56.153.171 is not registered with your OpenDNS dashboard network, so your individual settings do not take effect, because OpenDNS cannot recognize your DNS queries by your IP address.
  https://dashboard.opendns.com/settings/
  You want to sync your network with your correct IP address information, and you may flush your local resolver cache and your browser cache to make it work immediately.
  http://www.opendns.com/support/category/10
  And you'll want to install and run an Updater which automatically keeps your IP address information updated with your dashboard network going further.
  http://www.opendns.com/support/dynamic_ip_downloads/

  And besides, I really cannot confirm that "OpenDNS timing out and doesn't work"...

  0

  Comment actions Permalink
• 

  content2be September 22, 2013 02:24

  Thanks, Rotblitz, you're a gem!  I installed and ran the Updater, but as soon as I ran the Updater, it gave me the error message, "Your IP address is taken by another user."  And my network now shows as inactive. I sent a message to support as suggested by the KB article.  Anything else I should do?

  0

  Comment actions Permalink
• 

  maintenance September 22, 2013 05:05

  Yes, you may reboot your internet gateway in effort to get a new IP address, then  the Updater will update this new IP to your Dashboard for you.  If the error persists (aside from not getting a new IP from the ISP), there may yet be different issues with the addresses your ISP assigns.

   

   

  0

  Comment actions Permalink

Please sign in to leave a comment.