In anticipation of my arrival at XO, they modified their routing tables which caused theshore.net's DNS servers and websites to be unavailable. The problem was corrected this morning.

Thanks,
-Chris

IMHO, it's always a good idea to have a backup DNS server on a different network, in case such troubles arise. It might not be a bad idea to put one of the Linode DNS servers (or add a third DNS server) on HE's network to prevent this from happening again.

My Apache installation decided to shut down when it couldn't resolve its hostname after the daily log rotation. I've since added an entry into my /etc/hosts file to deal with this problem...

_________________
Bus error (passengers dumped)

That's in the works for my own domains.

I've been working under the assumption that all the distros pull their nameservers from the DHCP server. The DHCP servers at each datacenter are populated with the correct local DNS servers... But, Gentoo for example doesn't pull that info in -- it uses the default /etc/resolv.conf file from the template filesystem you installed from, which only has theshore's DNS servers...

It's a very good idea to add ThePlanet's or Hurricane's dns servers to your resolv.conf file if that's the case...

Name: ns1.theplanet.com
Address: 216.234.234.30

Name: ns2.theplanet.com
Address: 12.96.160.115

Name: ns1.he.net
Address: 216.218.130.2

Name: ns2.he.net
Address: 216.218.131.2

-Chris

Or you could install something like pdnsd and point it to the root DNS servers.

Adam

I run BIND in caching mode on my Linode, set to query the root name servers. When XO snafu'ed the routing to your DNS servers, *.linode.com was unresolvable worldwide, since both the primary and secondary nameservers were on the same route.

_________________
Bus error (passengers dumped)

I've registered two more dns servers on two additional networks (for a total of three different networks) for both theshore.net and linode.com.

That should take care of it!

-Chris