| PROVIDER | SERVERS |
| Microsoft | 131.107.1.240 |
| UUNET | 137.39.1.3
198.6.1.65
198.6.1.98
198.6.1.181 |
| Earthlink | 207.217.126.41
209.179.179.19 |
| Network
Solutions | 216.168.224.200
198.17.208.83
216.168.224.201 |
| Netcorps | 208.151.160.6 |
| Netscape | 198.95.251.10
207.200.73.80 |
|
You can find additional DNS servers provided you have a live
connection by typing whois website.com (of course
replace website.com with the real name) and it will give you a list of
name servers that the site provided to Network Solutions when the domain
was set up. Another way is to enter nslookup website.com and
you'll find out what name server is being used to find the answer. Whois
requires a Unix machine, while nslookup can be done from a Windows
machine. A way of TESTING the name servers is to enter telnet
X.X.X.X where X.X.X.X is the ip address of the nameserver. DO NOT USE
SERVER NAMES, USE THE NUMBERS. If you get a response of 'no route to host', it
may be down. If you get a 'connection refused' instead, you know it is up and
received your call. (Any self-respecting DNS server administrator would
configure the name server to refuse your telnet request, but the fact that you
received the reply implies you reached a working computer.) If on the other
hand you get no response at all on a number of these servers ('Trying X.X.X.X
...' and nothing further), then your issue is a dead connection (phone line
noise or POP troubles) and not a DNS server issue. |