object lesson in how *not* to manage DNS

tried to look at the Pacific Science Center’s website this morning . . . . couldn’t resolve their address.

Here’s why:


[/home/paul]:: dig pacsci.org ns


; <<>> DiG 8.3 <<>> pacsci.org ns
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2 ;; QUERY SECTION: ;; pacsci.org, type = NS, class = IN


;; ANSWER SECTION:
pacsci.org. 1d3h11s IN NS DNS1.pacsci.org.
pacsci.org. 1d3h11s IN NS DNS2.pacsci.org.


;; ADDITIONAL SECTION:
DNS1.pacsci.org. 1d4h25m28s IN A 204.29.25.5
DNS2.pacsci.org. 1d4h25m28s IN A 204.29.25.6


;; Total query time: 34 msec
;; FROM: blue.paulbeard.org to SERVER: default — 204.127.198.4
;; WHEN: Sun Dec 29 11:18:28 2002
;; MSG SIZE sent: 28 rcvd: 98

Both their name servers are on the same network segment and neither can be pinged. Having two next to each other is worse than having just one, since it leads to a false sense of security/redundancy. If something breaks connectivity or power to one, you lose both.