I ran into this problem a couple of years ago and pulled a little stunt to
fix it--haven't had a problem with it since. DNS lost its cached records
for the root-servers and could no longer find them to do lookups.
Go into your DNS Admin and create a new primary zone called "root-servers"
and add the following A and NS records (this is a couple years old, so you
may want to make sure that the IP addresses associated with the A records
are still correct):
root-servers.net. NS a.root-servers.net
root-servers.net. NS b.root-servers.net
root-servers.net. NS c.root-servers.net
root-servers.net. NS d.root-servers.net
root-servers.net. NS e.root-servers.net
root-servers.net. NS f.root-servers.net
root-servers.net. NS g.root-servers.net
root-servers.net. NS h.root-servers.net
root-servers.net. NS i.root-servers.net
root-servers.net. NS j.root-servers.net
root-servers.net. NS k.root-servers.net
root-servers.net. NS l.root-servers.net
root-servers.net. NS m.root-servers.net
a A 198.41.0.4
b A 128.9.0.107
c A 192.33.4.12
d A 128.8.10.90
e A 192.203.230.10
f A 192.5.5.241
g A 192.112.36.4
h A 128.63.2.53
i A 192.36.148.17
j A 198.41.0.10
k A 193.0.14.129
l A 198.32.64.12
m A 202.12.27.33
Josh Hillman
hillman@talstar.com
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart