[outages] AAAA for www.att.net broken?

[Frank Bulk (iname.com)]

I monitor ICMPv6 and HTTPv6 access to www.att.net, and starting at 1:26 am
Central I started getting no IPv6 address for that host.  (Because of ATT's
TTLs the DNS change may have happened earlier but our monitoring system
didn't see that).

It now has two CNAMEs, neither of which resolves to an IPv6 address.
www.att.net used to resolve to 2001:1890:1c01:2::40.  The IPv4 version goes
to att.yahoo.com, which does work.

If anyone from ATT/Akamai/Yahoo is lurking, could they look into this?

Regards,

Frank Bulk



root at nagios:/tmp# dig AAAA www.att.net

; <<>> DiG 9.7.3 <<>> AAAA www.att.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13552
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.att.net.                   IN      AAAA

;; ANSWER SECTION:
www.att.net.            180     IN      CNAME   www.att.net.edgekey.net.
www.att.net.edgekey.net. 2829   IN      CNAME   e8938.g.akamaiedge.net.

;; AUTHORITY SECTION:
g.akamaiedge.net.       640     IN      SOA     n0g.akamaiedge.net.
hostmaster.akamai.com. 1399462204 1000 1000 1000 1800

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed May  7 06:36:04 2014
;; MSG SIZE  rcvd: 157

root at nagios:/tmp#