This applies to customers on host9 through host16:

Hurricane Electric has informed me that this Friday, February 20th, 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)

nameserver 64.62.190.9
nameserver 65.19.175.2
nameserver 65.19.176.2
nameserver 65.19.174.2
nameserver 64.5.53.6
nameserver 216.156.129.65

The Bad Guys:

ns1.he.net 216.218.130.2
ns2.he.net 216.218.131.2
ns3.he.net 216.218.132.2

The Good Guys:

ns2.theshore.net 64.62.190.9 - HE-Linode (0 hops away)
ns1.fmt.he.net 65.19.175.2 - HE
ns2.fmt.he.net 65.19.176.2 - HE
ns1.sjc.he.net 65.19.174.2 - HE
ns1.theshore.net 64.5.53.6 - TP-Linode
ns.theshore.net 216.156.129.65 - XO-Linode

-Chris

A lot of people have been asking about their Linode unable to resolve dns lately -- so here's a reminder

-Chris

So... since it was last month.. and we aren't having problems, then we don't have to do anything?

Right. Just the people that had problems missed this posting, so I figured I'd remind people. I also added the recent "Linode Announcment" forum postings titles to the Open Ticket page...

-Chris

[raises hand]

Yep, I missed that posting.

Thanks caker.