Knowledge Base

Search the knowledge base

Knowledge Base > Troubleshooting

which.opendns.com instructions for checking server

To help diagnose technical problems, it's helpful to know which OpenDNS server, in which location, you are using. Since our anycasted nameserver addresses route you automatically to the closest servers, we offer a command line mechanism to determine this information.

Use which.opendns.com to learn this information. If you're not using OpenDNS, the response will share that information, too. What you are requesting is the which.opendns.com/TXT/IN record. (That's the Internet-class TXT record for which.opendns.com.)

Enter one of the following commands at the command line prompt on your machine - and do not enter the dollar ($) signs. 

$ dig +noall +answer which.opendns.com txt @208.67.222.222
OR
$ nslookup -type=txt which.opendns.com. 208.67.222.222

If you are using OpenDNS, you will get a response indicating the number and location of the server. Please share this with Support if you are having problems.

If you are not using OpenDNS, the response will include this text: "I am not an OpenDNS resolver."

Advanced: Forcing TCP instead of UDP

Some ISPs perform transparent proxying of port-53 UDP traffic. If you think that a command should be speaking to our server but its output indicates that it is not, try forcing the command to use TCP. 

$dig +vc +noall +answer which.opendns.com txt @208.67.222.222
OR 
$nslookup -vc -type=txt which.opendns.com. 208.67.222.222
Updated: October 30, 2007