This applies to customers on host9 through host16:[/size]
Hurricane Electric has informed me that this [b]Friday, February 20th[/b], ns1.he.net will be set to no recursion, meaning it will only answer DNS queries for domain zones HE’s dns servers are authorative for. Also, ns2.he.net and ns3.he.net have already been turned off.
Linode.com’s DHCP servers have been including a non-HE name server, ns.theshore.net which is on a remote network (XO) and might cause delays if left as the only working name server in your resolv.conf file.
The new name servers have been added in Linode.com’s DHCP server. If you use DHCP you should “cat /etc/resolv.conf” and look for “the bad guys” IP listed. You can get the correct configuration by one of the following methods: edit /etc/resolv.conf (see below), restart your networking, acquire a new DHCP lease, reboot your Linode.
Note to Gentoo users: Gentoo’s DHCP doesn’t seem to grab /etc/resolv.conf from DHCP. You’ve got to edit it manually.
Good /etc/resolv.conf (besides the search line)
The Bad Guys:
The Good Guys:
ns2.theshore.net 126.96.36.199 – HE-Linode (0 hops away)
ns1.fmt.he.net 188.8.131.52 – HE
ns2.fmt.he.net 184.108.40.206 – HE
ns1.sjc.he.net 220.127.116.11 – HE
ns1.theshore.net 18.104.22.168 – TP-Linode
ns.theshore.net 22.214.171.124 – XO-Linode
Filed under: datacenters by caker