Your IP:

Knowledge Base

Search the Knowledge Base

Knowledge Base

Error Messages

If you have received one of the following Error Messages while navigating the Internet or using OpenDNS, expand the message to understand the cause of the error and the known solutions to resolve it.

Dashboard Login Failure

If you experience problems when attempting to log in to the OpenDNS Dashboard, verify that you are accepting cookies from OpenDNS. If cookies are enabled and problems persist, try clearing the cache and the cookies of your Internet browser and retry.

SERVFAIL

The SERVFAIL error indicates that the nameserver of the requested domain is experiencing an internal error. OpenDNS servers are able to reach the domain but are unable to communicate with the specific nameserver. This can be the result of a few conditions such as unusually high traffic on that particular server. The only solution is to keep trying or try again later.

Network Already Exists / IP Address Taken by Another User / !Yours

These 3 errors are related to networks that use dynamic IP addresses, which have been or are currently registered with OpenDNS by another account holder.

The Network Already Exists error occurs when the IP address of your network was, at one time, previously registered with OpenDNS by a different account holder. Because many networks use dynamic IP addresses, the IP address is now assigned to your network, but still linked to the original OpenDNS account holder.

The Your IP Address Taken… or !Yours errors usually occur when updating your network IP address with the OpenDNS client-side IP updater. The conflict arises when the IP address being updated falls into one of the following two scenarios:
  1. Actual address is registered to another OpenDNS account holder.
  2. The IP address falls in the range of a larger netblock, which is registered with another OpenDNS account holder.

When these network conflicts occurs, not all OpenDNS features can be fully configured on your network, though you will still be using OpenDNS servers and benefiting from our fast, secure and reliable Internet experience.

To resolve this issue, please contact us with details. Be sure and include the following:
  • The error message
  • Your full name
  • The email address used to create the account
  • Your current IP address, found at the top of the OpenDNS home page
DNS and HTTP IP Address Mismatch (Content Filtering Not Working)

You may receive this error if you have just configured OpenDNS and are testing your configuration at our Welcome to OpenDNS test page. Typically, this issue will rectify itself within 3-5 minutes as the OpenDNS network registers your new network.

If it appears that your Web content filtering settings are no longer being applied to your network, and you have flushed DNS cache, this error is likely the result of an IP address conflict.

This error occurs when OpenDNS sees two different IP addresses: one IP address for DNS requests and a different IP address for HTTP (Web browsing) requests.

In rare cases, this error can occur if your IP address changed as the check for a new IP address was being conducted. However, in many situations this error occurs when your Internet connection is being sent through a proxy server. Check with your ISP to see if they use proxy servers for DNS or HTTP traffic. Many wireless and satellite broadband providers do use proxy servers.

OpenDNS Configuration Test Yields: “Oops!” Message

If you have tested your OpenDNS configuration and received the Oops! message, you may actually have OpenDNS configured correctly but be experiencing a problem related to how your ISP provisions your Internet connection.

First, check with your Internet Service Provider (ISP) to determine whether they allow third-party DNS services. If they do, the next most likely explanation for failing the OpenDNS configuration tests is that your ISP uses a proxy server.

If your ISP uses proxy servers, you will not be able to take advantage of our Web-based features, but you will still benefit from a fast, secure and reliable Internet navigation experience.

If the verification results from below indicate you are using different DNS servers and you are confident that you have followed the OpenDNS configuration instructions, please contact your ISP to verify whether they allow third-party DNS.

In some cases, a work-around has been found successful by configuring both the router/modem and all computers on the network to use OpenDNS servers. For more information about how to configure OpenDNS on a computer, follow this link.

To verify that you are using OpenDNS servers for DNS lookups, please go to the following instructions according to your computer's operating system.

Windows
To verify that you are using OpenDNS servers for DNS lookups, from your computer running Windows, follow these steps:
  1. Go to the Windows Start menu.
  2. Choose Run…
  3. In the Open: text box, type cmd.
  4. This opens the Windows terminal window.
  5. In the terminal window, after the prompt, type nslookup www.opendns.com.. (Be sure to include the trailing period after ".com.".)
  6. The results should look like the following:
    Server: resolver1.opendns.com or resolver2.opendns.com
    Address: 208.67.222.222 or 208.67.220.220

    Non-authoritative answer:
    Name: www.opendns.com
    Address: xxx.yyy.zzz.aaa

If the line including "Server" shows resolver1.opendns.com or resolver2.opendns.com and the associated IP addresses 208.67.222.222 or 208.67.220.220, respectively, then you are using OpenDNS for DNS lookups.

Mac
To verify that you are using OpenDNS servers for DNS lookups, from your computer running Mac OS, follow these steps:
  1. Launch the application Terminal, found in Applications -> Utilities on Mac OS X.
  2. Type dig www.opendns.com.
  3. If you are using OpenDNS, the results should look similar to the following:
    ;; <<>> DiG 9.2.4 <<>> www.opendns.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57481
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;;www.opendns.com. IN A ANSWER SECTION:
    ;;www.opendns.com. 30 IN A 208.67.219.101
    ;; Query time: 4 msec
    ;; SERVER: 208.67.222.222#53(208.67.222.222)
    ;; WHEN: Fri Jun 15 19:35:09 2007
    ;; MSG SIZE rcvd: 49
Linux
To verify that you are using OpenDNS servers for DNS lookups, from your computer running Mac OS, follow these steps:
  1. Bring up a terminal window.
  2. Type dig www.opendns.com.
  3. If you are using OpenDNS, the results should look similar to the following:
    ;; <<>> DiG 9.2.4 <<>> www.opendns.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57481
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;;www.opendns.com. IN A ANSWER SECTION:
    ;;www.opendns.com. 30 IN A 208.67.219.101
    ;; Query time: 4 msec
    ;; SERVER: 208.67.222.222#53(208.67.222.222)
    ;; WHEN: Fri Jun 15 19:35:09 2007
    ;; MSG SIZE rcvd: 49