John,
Thanks for the info/pointer to inet-access.
As far as I can tell, only www.foxnews.com, but there may be others.
Its the only one that was reported as an issue. Oddly, when I do a dig
against
it the response is as follows: (FYI this is from a linux system)
[EMAIL PROTECTED] log]# dig www.foxnews.com
; <<>> DiG 9.2.1 <<>> www.foxnews.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38652
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 9, ADDITIONAL: 0
;; QUESTION SECTION:
;www.foxnews.com. IN A
;; ANSWER SECTION:
www.foxnews.com. 3578 IN CNAME
www.foxnews.com.edgesuite.net.
www.foxnews.com.edgesuite.net. 21579 IN CNAME a20.g.akamai.net.
a20.g.akamai.net. 20 IN A 66.77.165.235
<===note the TTL of 20 secs
a20.g.akamai.net. 20 IN A 66.77.165.227 <===
and the num of Cnames
;; AUTHORITY SECTION:
g.akamai.net. 1779 IN NS n8g.akamai.net.
g.akamai.net. 1779 IN NS n0g.akamai.net.
g.akamai.net. 1779 IN NS n1g.akamai.net.
g.akamai.net. 1779 IN NS n2g.akamai.net.
g.akamai.net. 1779 IN NS n3g.akamai.net.
g.akamai.net. 1779 IN NS n4g.akamai.net.
g.akamai.net. 1779 IN NS n5g.akamai.net.
g.akamai.net. 1779 IN NS n6g.akamai.net.
g.akamai.net. 1779 IN NS n7g.akamai.net.
;; Query time: 130 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Sat Jul 10 12:56:52 2004
;; MSG SIZE rcvd: 297
Now, less than 4 minutes later I get this response:
[EMAIL PROTECTED] log]# dig www.foxnews.com
; <<>> DiG 9.2.1 <<>> www.foxnews.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44268
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 9, ADDITIONAL: 0
;; QUESTION SECTION:
;www.foxnews.com. IN A
;; ANSWER SECTION:
www.foxnews.com. 3361 IN CNAME
www.foxnews.com.edgesuite.net.
www.foxnews.com.edgesuite.net. 21362 IN CNAME a20.g.akamai.net.
a20.g.akamai.net. 20 IN A 66.77.165.225 <==
whoa, more CNames and they
a20.g.akamai.net. 20 IN A 66.77.165.227 <==
change every few minutes.
a20.g.akamai.net. 20 IN A 66.77.165.235
a20.g.akamai.net. 20 IN A 66.77.165.218
a20.g.akamai.net. 20 IN A 66.77.165.219
;; AUTHORITY SECTION:
g.akamai.net. 1562 IN NS n2g.akamai.net.
g.akamai.net. 1562 IN NS n3g.akamai.net.
g.akamai.net. 1562 IN NS n4g.akamai.net.
g.akamai.net. 1562 IN NS n5g.akamai.net.
g.akamai.net. 1562 IN NS n6g.akamai.net.
g.akamai.net. 1562 IN NS n7g.akamai.net.
g.akamai.net. 1562 IN NS n8g.akamai.net.
g.akamai.net. 1562 IN NS n0g.akamai.net.
g.akamai.net. 1562 IN NS n1g.akamai.net.
;; Query time: 17 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Sat Jul 10 13:00:29 2004
;; MSG SIZE rcvd: 345
While all this is going on, of course the MickeySoft DNSs do get messed up,
but
since I'm seeing it from various places and not just on my Biz IPOPs I was
wondering
if this might be fall out from the previous attack on Akamai.
Just odd I guess, and 1 more reason to push Nix as a DNS versus the M$
boxes.
Cheers
-Joe Blanchard
----- Original Message -----
From: "John Payne" <[EMAIL PROTECTED]>
To: "joe" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, July 10, 2004 12:55 AM
Subject: Re: DNS with Akamai
>
>
> On Jul 10, 2004, at 12:20 AM, joe wrote:
>
> >
> > Anyone noticing issues with Akamai and their DNS stuff?
> > Just wondering because I'm seeing strange responses regarding
> > www.foxnews.com, in that one of the Cnames a20.g.akamai.com
> > is changing every 20 seconds, and sometimes no response at all.
> >
>
> Is it just foxnews or other sites too? There's a thread on inet-access
> regarding foxnews and windows 2003 nameservers.
