David, Issue appears specific to one of five of AT&T's nameservers; in this case, ns3.attdns.com only. Authoritative nameservers for att.com are: ;; QUESTION SECTION: ;att.com. IN NS ;; ANSWER SECTION: att.com. 172800 IN NS ns1.attdns.com. att.com. 172800 IN NS ns2.attdns.com. att.com. 172800 IN NS ns3.attdns.com. att.com. 172800 IN NS ns4.attdns.com. att.com. 172800 IN NS ns5.attdns.com. ;; ADDITIONAL SECTION: ns1.attdns.com. 172800 IN A 144.160.112.22 ns2.attdns.com. 172800 IN A 144.160.128.140 ns3.attdns.com. 172800 IN A 144.160.20.47 ns4.attdns.com. 172800 IN A 192.128.167.75 ns5.attdns.com. 172800 IN A 192.128.133.75 I only get back NXDOMAIN from ns3.attdns.com. All the others work as expected. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | On Thu, Feb 15, 2007 at 08:56:01AM -0800, David Ulevitch wrote:

You broke the zone for ATT.com.

That's probably not good.

-david

$ dig @ns3.attdns.com att.com

; <<>> DiG 9.2.2 <<>> @ns3.attdns.com att.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 940 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;att.com. IN A

;; Query time: 75 msec ;; SERVER: 144.160.20.47#53(ns3.attdns.com) ;; WHEN: Thu Feb 15 08:54:58 2007 ;; MSG SIZE rcvd: 25