Search

Enter a search word or two and press return to see the search results.

Who am I?

Hi, I’m Graeme and these are my notes, from my messy desk. I started this blog because Google proved to be more useful at finding content than anything else I’ve used.

So I started adding my own content in the hopes that Google would index it and allow me to find things again in the future.

It works.

You can find out more about me here, and you should follow me on Twitter here.

Keeping up

You can automatically receive new content here by subscribing to the “Blog RSS” (link below). This is the easiest way to keep up with what I write here.  See this BBC article for a good introduction on RSS and keeping up with the goings on of the Internet more easily.

« Howto: Using Mail.app to archive your GMail email | Main | links for 2006-11-16 »
Monday
Nov202006

OMG! EXTREME CRITICAL EMERGENCY!! EVERYTHING'S BROKEN! People are DYING!

So my email isn't working this morning. Somehow the MX record for `woss.name` has, well, disappeared. Maybe [DreamHost](http://www.dreamhost.com/) got offended that I switched to [GMail](http://mail.google.com/) and decided to get their revenge. Maybe I buggered something up (I was doing stuff in the DH control panel yesterday afternoon, but I don't *think* I touched `woss.name`). Or maybe the gremlins got to it.

Nevertheless I've reinstated the record through the web panel about half an hour ago, though it's still not showing up in reality. This means my personal email is all bouncing with 'relay denied' because after failing to find an MX record, one falls back to the A record, which is one of DH's web servers and doesn't relay mail.

Looks like, if you want to contact me today, best try or IM instead...

**Update** It looks very much like something is buggered at DH. I last received an email to my `woss.name` address at about 07:00 this morning (those irritating cron messages do have a use after all!), which means the first definite failure was 08:00. DH's MX records are set with a TTL of 14400 seconds (4 hours), which suggests something happened to the MX record sometime between 04:00 and 08:00 GMT. Trust me, I was asleep then. :-)

Also, it looks very much like DH's back end systems are not actually updating their DNS servers. The new MX record is showing up in their web panel but over an hour after I first made the change (I've subsequently added a couple of spurious DNS records since then to try and prod it along), [dnscheck](http://www.squish.net/dnscheck/) still shows:

> 33.3% of queries will end in failure at 66.33.206.206 (ns1.dreamhost.com) - no such record
>
> 33.3% of queries will end in failure at 66.201.54.66 (ns2.dreamhost.com) - no such record
>
> 33.3% of queries will end in failure at 66.33.216.216 (ns3.dreamhost.com) - no such record

which means it's failing to resolve the MX and resorting back to the A record.

Argh!

**Update 2**: Well, it looks like nearly 5 hours later it's actually propagated to one of their three NS servers. So you currently have about a 1 in 3 chance of me receiving your email. So now you've got to ask yourself a question: "Do I feel lucky?" Well, do ya, punk?

*sigh* I think I need a service provider in the same time zone as me.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (2)

[...] Register « OMG! EXTREME CRITICAL EMERGENCY!! EVERYTHING’S BROKEN! People are DYING! [...]

Have you considered everydns.net? It's by the same people as opendns.com and offers hosting of DNS on four servers through-out the world for free.

November 20, 2006 | Unregistered Commenterpaul

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>