Open DNS not working???

Comments

37 comments

  • Avatar
    Anthony Honciano

    Hi there,

    I'm sorry to hear that you're experiencing difficulties. I was able to take a look at your account, and it appears that your IP address is not reporting any traffic. According to your settings, your network is set as a dynamic IP address, do you have the IP Updater installed on a computer that is connected to your network? The application can be downloaded from http://www.opendns.com/support/article/87, this will automatically update your account when your public IP address changes.

    You can also make the change at your dashboard at https://dashboard.opendns.com/settings, if the IP address in your network doesn't match what is displayed at the top of the site, there should be a green refresh icon next to your network that will help you update your IP address.

    To ensure that OpenDNS is working properly for you after these changes, please flush your browser and DNS cache by following the instructions below:

    http://www.opendns.com/support/article/67
    http://www.opendns.com/support/article/68

    Let us know if you have any questions and we'll be happy to help you.

    Best regards,

    Anthony Honciano
    Customer Support Representative
    OpenDNS, Inc

  • Avatar
    k.a.b

    I have the same issue and I did everything you suggested. What else could be the issue?

     

    Kelly

  • Avatar
    Kristy Patullo

    Kelly, I'm starting to see traffic from your network, would you please visit opendns.com/welcome/ to check if you are using OpenDNS?  Also, while on your home network make sure that the IP address at the top of your dashboard where it saysYour Current IP is matches the one registered in your dashboard as your network.

  • Avatar
    gkmchardy

    I followed all of Anthony's steps, but as yet OpenDNS is not blocking anything. It appears not to have connected since November 17. The IP number at the top of the screen does match the IP address of my network listed on the dashboard. What to do next?

  • Avatar
    mattwilson9090

    You've flushed the cache following the directions above?

    Have you also visited opendns.com/welcome?

    You do have categories checked to block, or have domains blocked in your blacklist, correct?

  • Avatar
    camptuckahoe544

    Currently having the same issues as well.. Not sure whats happening here today?

  • Avatar
    mattwilson9090

    Have you tried following any of the troubleshooting that this other person was told to do more than 6 months ago? Answer the same questions that were posed to the original poster as well.

  • Avatar
    camptuckahoe544

    Indeed I have. I have found that the OpenDNS Prem. accounts I have are having issues, while my one free account is not. Everything is working as it should. 

  • Avatar
    rotblitz

    "Indeed I have."

    Great!  So you're saying you have visited http://welcome.opendns.com/ from the networks/devices you're facing problems?  What was the outcome?

    And you're also saying that your IP address information is correctly registered at https://dashboard.opendns.com/settings/ separately for the dashboard networks you're having troubles with?

  • Avatar
    camptuckahoe544

    I get the welcome with the check mark stating that I am using OpenDNS. I can block Phishing but not any categories. I have three (3) accounts total for two different properties. 2 OpenDNS Premium that are NOT working. Same results and everything listed above. The Free one is working as it should be. 

  • Avatar
    rotblitz

    "I get the welcome with the check mark stating that I am using OpenDNS. I can block Phishing but not any categories."

    That indicates that you're using OpenDNS with the defaults, not with your individual dashboard settings.  OpenDNS is unable to associate your DNS queries with your accounts.  This happens when your IP addresses are not registered with your dashboard.

    "I have three (3) accounts total for two different properties."

    The number of locations doesn't matter, but only the number of your public IP addresses.  You can have one dashboard network for each public IP address, no matter if for the free service or for VIP.

    All that said, check again that your correct public IP addresses are registered with each of your dashboard networks.  You find out each IP address by executing the following command within the network you're going to check it's related dashboard.

       nslookup myip.opendns.com.

    Only the output of this command shows reliably what IP address OpenDNS sees from your DNS lookups, not what any website or router may show up with.
    If the output is "Non-existent domain", then you don't use OpenDNS at al on that device.

  • Avatar
    camptuckahoe544

    When I go to the Dashboard, it claims that it is registered to the account appropriately. However the nslookup myip.opendns.com claims that its not working properly? Not sure how this is happening when your using it on the LAN and WAN address. 

  • Avatar
    camptuckahoe544

    The computers are seeing the OpenDNS address of 208.67.222.222 and 208.67.220.220

  • Avatar
    rotblitz

    "However the nslookup myip.opendns.com claims that its not working properly?"

    Why does it "claim" this?  What exactly happened?

    "The computers are seeing the OpenDNS address of 208.67.222.222 and 208.67.220.220"

    How are the computers "seeing" these addresses?  These are the OpenDNS resolver addresses, to be configured on the router or on the end user devices.  These devices do not "see" anything.  They are blind without eyes.

    To better understand what's going on with your problem, copy & paste the complete plain text output of the following diagnostic commands, taken from a network where OpenDNS doesn't work:

       nslookup -type=txt debug.opendns.com.

       nslookup -type=txt debug.opendns.com. 208.67.222.220

    I may be able to see where the problem lies then.

  • Avatar
    camptuckahoe544

    The DNS Addresses are setup on the CentryLink C2000T modem. Both on LAN and WAN configurations. 

    DNS timed out on the nslookup per your request. 

     

  • Avatar
    rotblitz

    "Both on LAN and WAN configurations."

    This is most likely overdone, but shouldn't prevent from using OpenDNS.

    "DNS timed out on the nslookup per your request. "

    Then try this variation of the commands:

       nslookup -timeout=12 -type=txt debug.opendns.com.

       nslookup -timeout=12 -type=txt debug.opendns.com. 208.67.222.220

    If you still get timeouts for both commands, copy & paste the complete plain text output of the following command:

       ipconfig /all

    Because of the unusual timeouts, you may also want to post the output of the following command if you want me to look at the timeout problem:

       tracert 208.67.222.220

    Think about to take all of these commands from the network where OpenDNS does not work for you.

  • Avatar
    Hidden Valley Scout Reservation

    Tracing route to resolver3.opendns.com [208.67.222.220]
    over a maximum of 30 hops:

      1    <1 ms     1 ms     2 ms  192.168.0.1
      2    21 ms    22 ms    22 ms  pa-67-234-216-1.dhcp.embarqhsd.net [67.234.216.
    ]
      3    21 ms    25 ms    25 ms  crls-agw1.inet.qwest.net [75.160.220.17]
      4    39 ms    41 ms    40 ms  chp-brdr-03.inet.qwest.net [67.14.8.190]
      5    39 ms    38 ms    39 ms  ae5.chi12.ip4.gtt.net [173.205.63.229]
      6    41 ms    40 ms    40 ms  xe-1-2-0.chi11.ip4.gtt.net [141.136.107.189]
      7    40 ms    43 ms    40 ms  opendns-gw.ip4.gtt.net [216.221.158.198]
      8    41 ms    43 ms    40 ms  resolver3.opendns.com [208.67.222.220]

    Trace complete.

  • Avatar
    rotblitz

    @Hidden Valley Scout Reservation
    Are you the same person as camptuckahoe544?  There's nothing wrong with your traceroute.

    @camptuckahoe544
    If you need more help, you'd to post the other commands as well.

  • Avatar
    camptuckahoe544

    Yeah Hidden Valley and Camp Tuckahoe are still me, I was running the trace route by accident from the other account. So everything is working as it should be?

  • Avatar
    rotblitz

    The traceroute was to show where the timeouts might be coming from.  But it didn't explain it.

    You said you had the "same issues" as the original poster, meaning your content filtering and stats did not work.    I cannot know if everything is working now, only you can know.

  • Avatar
    camptuckahoe544

    Currently at this time, its still not working. Not sure where else to look. 

  • Avatar
    rotblitz

    I said what command outputs I need to see to help futher, so do so as advised.

  • Avatar
    Hidden Valley Scout Reservation

    C:\Users\Camp Director>nslookup - timeout=12 -type=txt debug.opendns.com
    Usage:
       nslookup [-opt ...]             # interactive mode using default server
       nslookup [-opt ...] - server    # interactive mode using 'server'
       nslookup [-opt ...] host        # just look up 'host' using default server
       nslookup [-opt ...] host server # just look up 'host' using 'server'

    and...

     

    C:\Users\Camp Director>nslookup -timeout=12 -type=txt debug.opendns.com. 208.67.
    222.220
    Server:  resolver3.opendns.com
    Address:  208.67.222.220

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

            "server 11.chi"
    debug.opendns.com       text =

            "flags 20 0 70 5950800000000000000"
    debug.opendns.com       text =

            "originid 0"
    debug.opendns.com       text =

            "actype 0"
    debug.opendns.com       text =

            "source 67.234.221.109:51250"

     

     

     

     

     

     

  • Avatar
    Hidden Valley Scout Reservation


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : CampDirector-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : domain
       Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E
     Gigabit Ethernet NIC (NDIS 6.20)
       Physical Address. . . . . . . . . : 00-25-64-E5-DA-E0
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::a455:c80b:f07f:e8e9%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, December 13, 2015 10:16:23 PM
       Lease Expires . . . . . . . . . . : Sunday, December 20, 2015 11:46:26 AM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 234890596
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-0F-6C-DB-00-25-64-E5-DA-E0

       DNS Servers . . . . . . . . . . . : 208.67.222.222
                                           208.67.220.220
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.domain:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : domain
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Camp Director>ipconfig /all

     

     

     

  • Avatar
    rotblitz

    The first command "nslookup - timeout=12 -type=txt debug.opendns.com." failed, because there was a space between - and timeout, therefore the usage was explained.

    The second nslookup shows that your IP address 67.234.221.109 is not registered with your network at https://dashboard.opendns.com/settings/
    Therefore OpenDNS cannot associate your DNS queries with your dashboard settings, and your settings cannot take effect.  If you fix this, content filtering and stats will work, and your problems should have gone.

    "When I go to the Dashboard, it claims that it is registered to the account appropriately."

    Therefore this statement is not correct.

    The "ipconfig /all" output shows that your PC is connected via cable to the router, and that you have configured the OpenDNS resolver addresses on the PC.  That's fine.

  • Avatar
    Hidden Valley Scout Reservation

    C:\Users\Camp Director>nslookup -timeout=12 -type=txt debug.opendns.com
    Server:  resolver1.opendns.com
    Address:  208.67.222.222

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

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

            "flags 20 0 70 5950800000000000000"
    debug.opendns.com       text =

            "originid 0"
    debug.opendns.com       text =

            "actype 0"
    debug.opendns.com       text =

            "source 67.234.221.109:51293"

    C:\Users\Camp Director>"nslookup - timeout=12 -type=txt debug.opendns.com"

  • Avatar
    Hidden Valley Scout Reservation

    Please see attachments as I provided from my Dashboard settings as well.




    capture 3.JPG
    Capture 2.JPG
    capture 6.JPG
    capture 5.JPG
    Screen 1.JPG
    capture 4.JPG
  • Avatar
    Hidden Valley Scout Reservation

    I also provided screenshots of my Router/Modem provided by CenturyLink T2000 series. 




    capture 7.JPG
    capture 10.JPG
    capture 8.JPG
    capture 9.JPG
  • Avatar
    mattwilson9090

    One thing you *MUST* do is disable IPv6 on the router. It's entirely likely that all of your DNS traffic is going out via IPv6, in which case OpenDNS will not receive or process any of it for filtering. Even if you were using the OpenDNS IPv6 "sandbox" addresses, which you aren't, those only support name resolution, not filtering or any other services.

    Once your traffic is going out via IPv4 to OpenDNS, about 24 hours your stats will start populating.

  • Avatar
    Hidden Valley Scout Reservation

    Contacted my service provider and found out they made a mistake with turning it on. It is now off and its tested, still doesn't work. Screenshots are attached for review. 




    Capture 11.JPG
    Capture 12.JPG

Please sign in to leave a comment.