best SOA evar!

[fanf]

; <<>> DiG 9.2.4 <<>> soa figure53.com. @ns1.dreamhost.com.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26927
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;figure53.com.                  IN      SOA

;; ANSWER SECTION:
figure53.com.           14400   IN      SOA     2007081700. 21487. 1800 1814400 14400 604800 3600

;; Query time: 153 msec
;; SERVER: 66.33.206.206#53(ns1.dreamhost.com.)
;; WHEN: Thu Aug 23 22:42:10 2007
;; MSG SIZE  rcvd: 81

Comments

[mas90.livejournal.com]

*giggle*

[nibot.livejournal.com]

?

[kaet.livejournal.com]

Is that really clever, or really dumb. I don't know enough bind to be sure. But they put the periods in, so they must have known they weren't typing in numbers?

[mas90.livejournal.com]

They've missed out the first two fields. What they intended to be the serial number has been interpreted as the primary nameserver address, and so on. The last two fields have been filled in with defaults. The periods were probably added by the primary nameserver trying to make sense of a broken zonefile.

I wonder whether anything (erroneously) interprets the primary nameserver field as the decimal word representation of an IP address (119.161.162.228)...

[gerald_duck]

I'm getting rusty.

I could see at a glance the administrative e-mail address was missing, but I couldn't remember which field it was. Oh, for good old fashioned nslookup with its commented output.

[ronebofh.livejournal.com]

I suspect that they updated it with a buggy script, and they neglected to include the primary nameserver and the administrative e-mail address. The script took the first two arguments (the would-be serial number and refresh period), added dots, and threw in defaults for the last two values.

[kaet.livejournal.com]

Happy Birthday!

[cozminsky.livejournal.com]

It's not like the SOA is really useful unless you're using zone transfers anyway. I'd imagine dreamhost would be using some kind of multi-master system pulling data from a central database anyway.

[fanf]

The minimum TTL in the SOA is also used for negative cacheing.

This was just the most amusing error in their DNS that I spotted. The zone's nameservers were lame and/or serving none of the expected RR sets, e.g. A, MX and even NS.