dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2385

SLC 96
join:2005-04-03
Chicago, IL

SLC 96

Member

[IPv6] Comcast IPv6 DNS server down

I cant get to 2001:558:FEED::1 but 2001:558:FEED::2 is reachable.

whfsdude
Premium Member
join:2003-04-05
Washington, DC

whfsdude

Premium Member

[IPv6] Re: Comcast IPv6 DNS server down

Those are anycast addresses. Can you traceroute6 2001:558:FEED::2 to see which node you reach.

SLC 96
join:2005-04-03
Chicago, IL

SLC 96

Member

$ traceroute6 2001:558:FEED::2
traceroute6 to 2001:558:FEED::2 (2001:558:feed::2) 64 hops max, 12 byte packets
1
2 * * *
3 xe-0-1-0-32767-sur01.birmingham.mi.michigan.comcast.net 12.667 ms 9.434 ms 11.577 ms
4 te-0-11-0-1-ar01.taylor.mi.michigan.comcast.net 12.800 ms 11.995 ms 12.749 ms
5 te-9-4-ur01.westlandrdc.mi.michigan.comcast.net 15.346 ms 12.279 ms 18.984 ms
6 cdns02.comcast.net 12.943 ms 13.245 ms 14.548 ms

$ traceroute6 2001:558:FEED::1
traceroute6 to 2001:558:FEED::1 (2001:558:feed::1) 64 hops max, 12 byte packets
1
2 * * *
3 xe-0-1-0-32767-sur01.birmingham.mi.michigan.comcast.net 12.844 ms 23.751 ms 10.670 ms
4 te-0-11-0-1-ar01.pontiac.mi.michigan.comcast.net 12.870 ms 11.366 ms 11.956 ms
5 he-4-4-0-0-cr01.350ecermak.il.ibone.comcast.net 17.603 ms
he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net 21.441 ms 21.556 ms
6 he-2-14-0-0-ar01.area4.il.chicago.comcast.net 21.789 ms 21.737 ms 20.169 ms
7 te-9-1-ur09-d.area4.il.chicago.comcast.net 19.164 ms 19.885 ms 18.062 ms
8 te-8-1-ur08-d.area4.il.chicago.comcast.net 19.270 ms 17.728 ms 16.923 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer to SLC 96

Premium Member

to SLC 96

Re: [IPv6] Comcast IPv6 DNS server down

said by SLC 96:

I cant get to 2001:558:FEED::1 but 2001:558:FEED::2 is reachable.

It is not just you who sees this. I can't ping 2001:558:FEED::1 or use it for DNS queries either:

C:\>ping 2001:558:FEED::1
 
Pinging 2001:558:feed::1 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 2001:558:feed::1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>dig -taaaa www.comcast.net @2001:558:FEED::1
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @2001:558:FEED::1
;; global options: +cmd
;; connection timed out; no servers could be reached
 
C:\>ping 2001:558:FEED::2
 
Pinging 2001:558:feed::2 with 32 bytes of data:
 
Reply from 2001:558:feed::2: time=32ms
Reply from 2001:558:feed::2: time=36ms
Reply from 2001:558:feed::2: time=32ms
Reply from 2001:558:feed::2: time=33ms
 
Ping statistics for 2001:558:feed::2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 36ms, Average = 33ms
 
C:\>dig -taaaa www.comcast.net @2001:558:FEED::2
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @2001:558:FEED::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58957
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.comcast.net.               IN      AAAA
 
;; ANSWER SECTION:
www.comcast.net.        47      IN      CNAME   www.comcast.net.edgesuite.net.
www.comcast.net.edgesuite.net. 170 IN   CNAME   a1526.dscg.akamai.net.
a1526.dscg.akamai.net.  18      IN      AAAA    2600:1407:11::174a:9c7
a1526.dscg.akamai.net.  18      IN      AAAA    2600:1407:11::174a:9d6
 
;; Query time: 31 msec
;; SERVER: 2001:558:feed::2#53(2001:558:feed::2)
;; WHEN: Tue Aug 19 17:00:12 2014
;; MSG SIZE  rcvd: 172
 

And unfortunately »dns.comcast.net/ is also not responding, so there is no way to get status information from Comcast either.

ropeguru
Premium Member
join:2001-01-25
Mechanicsville, VA

ropeguru to SLC 96

Premium Member

to SLC 96
Both are responding from my connection here.

plencnerb
Premium Member
join:2000-09-25
53403-1242

plencnerb to SLC 96

Premium Member

to SLC 96
I also noticed that

http://www.comcast6.net/
 

which, used to look like this (btw, google search image, not one that I saved)




Now re-directs me to
http://xfinity.comcast.net/
 

which looks like this




It is also worth to note that doing a google search on "http://www.comcast6.net/" results in this. Take note of the top two results.




--Brian

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer to ropeguru

Premium Member

to ropeguru
said by ropeguru:

Both are responding from my connection here.

Ahh, the magic of Anycast -- 2001:558:FEED::1 is still not responding to ICMP echo or DNS queries from my location in Murfreesboro, TN:

C:\>ping 2001:558:FEED::1
 
Pinging 2001:558:feed::1 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 2001:558:feed::1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>dig -taaaa my.yahoo.com @2001:558:FEED::1
 
; <<>> DiG 9.9.2 <<>> -taaaa my.yahoo.com @2001:558:FEED::1
;; global options: +cmd
;; connection timed out; no servers could be reached
 
C:\>ping 2001:558:FEED::2
 
Pinging 2001:558:feed::2 with 32 bytes of data:
 
Reply from 2001:558:feed::2: time=33ms
Reply from 2001:558:feed::2: time=33ms
Reply from 2001:558:feed::2: time=33ms
Reply from 2001:558:feed::2: time=39ms
 
Ping statistics for 2001:558:feed::2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 39ms, Average = 34ms
 
C:\>dig -taaaa my.yahoo.com @2001:558:FEED::2
 
; <<>> DiG 9.9.2 <<>> -taaaa my.yahoo.com @2001:558:FEED::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48754
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;my.yahoo.com.                  IN      AAAA
 
;; ANSWER SECTION:
my.yahoo.com.           9       IN      CNAME   fd-fp3.wg1.b.yahoo.com.
fd-fp3.wg1.b.yahoo.com. 186     IN      CNAME   ds-fp3.wg1.b.yahoo.com.
ds-fp3.wg1.b.yahoo.com. 6       IN      CNAME   ds-any-fp3-lfb.wa1.b.yahoo.com.
ds-any-fp3-lfb.wa1.b.yahoo.com. 186 IN  CNAME   ds-any-fp3-real.wa1.b.yahoo.com.
ds-any-fp3-real.wa1.b.yahoo.com. 39 IN  AAAA    2001:4998:44:4::c:9102
ds-any-fp3-real.wa1.b.yahoo.com. 39 IN  AAAA    2001:4998:f00d:1fe::3001
ds-any-fp3-real.wa1.b.yahoo.com. 39 IN  AAAA    2001:4998:44:4::c:9101
ds-any-fp3-real.wa1.b.yahoo.com. 39 IN  AAAA    2001:4998:f00d:1fe::3000
 
;; Query time: 46 msec
;; SERVER: 2001:558:feed::2#53(2001:558:feed::2)
;; WHEN: Tue Aug 19 21:04:40 2014
;; MSG SIZE  rcvd: 264
 

It looks as if Comcast's Anycast is sending me to a server in Westland, MI for 2001:558:feed::2, and is possibly trying to send me to a server in Chicago, IL for 2001:558:feed::1:

C:\>tracert 2001:558:FEED::1
 
Tracing route to cdns01.comcast.net [2001:558:feed::1]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2601:5:1f00:ac7:1e7e:e5ff:fe4c:e6ff
  2     9 ms     8 ms     9 ms  2001:558:6016:3e::1
  3     8 ms     8 ms     8 ms  xe-10-0-1-32767-sur03.murfreesboro.tn.nash.comcast.net [2001:558:162:98::1]
  4     9 ms    12 ms    12 ms  xe-2-0-8-0-ar03.nashville.tn.nash.comcast.net [2001:558:160:a::1]
  5    25 ms    31 ms    24 ms  he-2-13-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f691::1]
  6    24 ms    24 ms    39 ms  he-0-13-0-0-ar01.area4.il.chicago.comcast.net [2001:558:0:f79f::2]
  7    23 ms    22 ms    30 ms  te-9-1-ur09-d.area4.il.chicago.comcast.net [2001:558:300:52::1]
  8    23 ms    22 ms    21 ms  te-8-3-ur08-d.area4.il.chicago.comcast.net [2001:558:300:e9::1]
  9     *       22 ms     *     te-9-2-ur05-d.area4.il.chicago.comcast.net [2001:558:300:54::2]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *     ^C
C:\>tracert 2001:558:FEED::2
 
Tracing route to cdns02.comcast.net [2001:558:feed::2]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2601:5:1f00:ac7:1e7e:e5ff:fe4c:e6ff
  2     8 ms     9 ms    10 ms  2001:558:6016:3e::1
  3    16 ms     9 ms     8 ms  xe-10-0-1-32767-sur03.murfreesboro.tn.nash.comcast.net [2001:558:162:98::1]
  4    13 ms     9 ms    10 ms  xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [2001:558:160:95::1]
  5    24 ms    23 ms    23 ms  he-2-13-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f691::1]
  6    30 ms    29 ms    28 ms  2001:558:0:f926::2
  7    32 ms    39 ms    33 ms  te-9-4-ur02-d.westlandrdc.mi.michigan.comcast.net [2001:558:110:59::2]
  8    34 ms    32 ms    32 ms  cdns02.comcast.net [2001:558:feed::2]
 
Trace complete.
 

ropeguru
Premium Member
join:2001-01-25
Mechanicsville, VA

ropeguru

Premium Member

My traceroutes:

traceroute6 2001:558:feed::1
traceroute to 2001:558:feed::1 (2001:558:feed::1) from 2601:8:1400:880:39b4:f6ab:2a6:3a18, 30 hops max, 24 byte packets
 1  2601:8:1400:880::1 (2601:8:1400:880::1)  0.412 ms  0.263 ms  0.26 ms
 2  * * *
 3  * * *
 4  te-1-3-ur01.shadygrove.va.richmond.comcast.net (2001:558:182:fc::1)  8.088 ms  8.935 ms  8.961 ms
 5  xe-12-0-1-0-ar02.charlvilleco.va.richmond.comcast.net (2001:558:180:26::1)  16.897 ms  17.435 ms  16.93 ms
 6  pos-1-5-0-0-cr01.ashburn.va.ibone.comcast.net (2001:558:0:f7d1::1)  19.365 ms  21.702 ms  19.873 ms
 7  2001:558:0:f786::2 (2001:558:0:f786::2)  20.938 ms  21.719 ms  21.175 ms
 8  2001:558:340:23b::2 (2001:558:340:23b::2)  20.836 ms  21.583 ms  23.158 ms
 9  te-3-2-ur03-d.manassascc.va.bad.comcast.net (2001:558:340:12b::2)  23.761 ms  22.849 ms  22.477 ms
10  cdns01.comcast.net (2001:558:feed::1)  27.645 ms  27.583 ms  27.489 ms
 
traceroute6 2001:558:feed::2
traceroute to 2001:558:feed::2 (2001:558:feed::2) from 2601:8:1400:880:39b4:f6ab:2a6:3a18, 30 hops max, 24 byte packets
 1  2601:8:1400:880::1 (2601:8:1400:880::1)  0.479 ms  0.306 ms  0.278 ms
 2  * * *
 3  * * *
 4  te-1-3-ur01.shadygrove.va.richmond.comcast.net (2001:558:182:fc::1)  12.257 ms  9.393 ms  9.074 ms
 5  xe-12-0-1-0-ar02.charlvilleco.va.richmond.comcast.net (2001:558:180:26::1)  16.384 ms  16.73 ms  20.369 ms
 6  2001:558:0:f929::1 (2001:558:0:f929::1)  20.779 ms  21.015 ms  20.155 ms
 7  he-0-14-0-0-ar03.mckeesport.pa.pitt.comcast.net (2001:558:0:f7a9::2)  26.344 ms  25.406 ms  26.266 ms
 8  te-1-1-ur02-d.summitpark.pa.pitt.comcast.net (2001:558:380:5::2)  26.767 ms  29.2 ms  27.338 ms
 9  cdns02.comcast.net (2001:558:feed::2)  25.716 ms  26.843 ms  26.169 ms
 

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer

Premium Member

said by ropeguru:

My traceroutes:
---
---

Anycast is great (when it works). It looks as if the OP and myself are just stuck with being redirected to a dead server in Chicago for 2001:558:feed::1
grod46
join:2012-11-25
Fresno, CA

grod46 to SLC 96

Member

to SLC 96
Here is my traceroute to 2001:558:feed::1

Tracing route to cdns01.comcast.net [2001:558:feed::1] over a maximum of 30 hops:

1 5 ms 2 ms 1 ms 2601:c:8300:341:16cf:e2ff:fef6:1be1
2 * * * Request timed out.
3 17 ms 18 ms 17 ms ge-1-10-sr01.mendota.ca.ccal.comcast.net [2001:558:1a2:76::1]
4 19 ms 23 ms 21 ms te-8-1-ur01.shaw.ca.ccal.comcast.net [2001:558:210:7a::1]
5 25 ms 31 ms 38 ms 2001:558:210:ad::1
6 40 ms 40 ms 30 ms be-60-ar01.oakland.ca.sfba.comcast.net [2001:558:80:1::1]
7 25 ms 21 ms 20 ms te-4-4-ur02-d.sanjose.ca.sfba.comcast.net [2001:558:80:377::2]
8 54 ms 21 ms 21 ms cdns01.comcast.net [2001:558:feed::1]

Trace complete.

THZNDUP
Deorum Offensa Diis Curae
Premium Member
join:2003-09-18
Lard

1 edit

THZNDUP to plencnerb

Premium Member

to plencnerb
comcast6.net is being relocated per jlivingood See Profile's rather cryptic post........
»[IPv6] Comcast6.net

I'd try to help with the ipv6 addresses but my Netgear router's IPv6 went tu again and I don't care to fool with it for a while................

Guess I lied, tried a quick reset adapter and got IPv6 back(for a few minutes so far) and can reach both FEED::1 and FEED::2 from Central valley in CA

SLC 96
join:2005-04-03
Chicago, IL

SLC 96 to grod46

Member

to grod46
Still down for me.

RR Conductor
Ridin' the rails
Premium Member
join:2002-04-02
Redwood Valley, CA

RR Conductor to SLC 96

Premium Member

to SLC 96
Both of those are reachable to me here in Northwestern California.

mb6
join:2000-07-23
Washington, NJ
Netgear CM1150V
Netgear R7800

mb6 to SLC 96

Member

to SLC 96
For me, Feed 1 is located in Delaware and times out. Feed 2 is located in Pittsburg and pings OK

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Mark>ping 2001:558:FEED::2

Pinging 2001:558:feed::2 with 32 bytes of data:
Reply from 2001:558:feed::2: time=38ms
Reply from 2001:558:feed::2: time=22ms
Reply from 2001:558:feed::2: time=21ms
Reply from 2001:558:feed::2: time=22ms

Ping statistics for 2001:558:feed::2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 38ms, Average = 25ms

C:\Users\Mark>ping 2001:558:FEED::1

Pinging 2001:558:feed::1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:558:feed::1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Mark>

fuziwuzi
Not born yesterday
Premium Member
join:2005-07-01
Palm Springs, CA

fuziwuzi to SLC 96

Premium Member

to SLC 96
I gave up on Comcast DNS a long time ago, just too unstable. I hard-code Google DNS for both IPv4 and IPv6 into my Linksys E3000 running TomatoUSB Shibby.

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

1 recommendation

NetFixer

Premium Member

said by fuziwuzi:

I gave up on Comcast DNS a long time ago, just too unstable. I hard-code Google DNS for both IPv4 and IPv6 into my Linksys E3000 running TomatoUSB Shibby.

I have found that their DNSSEC is generally as reliable as anyone's DNS. OTOH, they are still experimenting with IPv6, and I do frequently run into anomalies with their IPv6 implementation. For that reason, I don't use their IPv6 Anycast IP addresses for DNS resolution; I just use their IPv4 75.75.75.75 and 75.75.76.76 Anycast addresses for both IPv4 and IPv6 DNS resolution. I can't recall having had any Comcast related DNS problems since they moved to DNSSEC (but then again, I use my own DNS server as the primary, and it uses the Comcast servers for external resolution (so even if one of their IPv4 Anycast addresses stopped functioning, I would not notice it unless I looked at my own DNS server logs).

And as you can see below, it is only one of the IPv6 addresses that is failing:

C:\>dig -taaaa www.comcast.net @2001:558:feed::1
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @2001:558:feed::1
;; global options: +cmd
;; connection timed out; no servers could be reached
 
C:\>dig -taaaa www.comcast.net @2001:558:feed::2
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @2001:558:feed::2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5943
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.comcast.net.               IN      AAAA
 
;; ANSWER SECTION:
www.comcast.net.        89      IN      CNAME   www.comcast.net.edgesuite.net.
www.comcast.net.edgesuite.net. 79 IN    CNAME   a1526.dscg.akamai.net.
a1526.dscg.akamai.net.  1       IN      AAAA    2600:1407:11::174a:9d6
a1526.dscg.akamai.net.  1       IN      AAAA    2600:1407:11::174a:9b0
 
;; Query time: 31 msec
;; SERVER: 2001:558:feed::2#53(2001:558:feed::2)
;; WHEN: Wed Aug 20 12:04:14 2014
;; MSG SIZE  rcvd: 172
 
C:\>dig -taaaa www.comcast.net @75.75.75.75
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @75.75.75.75
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15258
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.comcast.net.               IN      AAAA
 
;; ANSWER SECTION:
www.comcast.net.        42      IN      CNAME   www.comcast.net.edgesuite.net.
www.comcast.net.edgesuite.net. 25 IN    CNAME   a1526.dscg.akamai.net.
a1526.dscg.akamai.net.  17      IN      AAAA    2600:1402:e::b833:96a0
a1526.dscg.akamai.net.  17      IN      AAAA    2600:1402:e::b833:9698
 
;; Query time: 31 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Wed Aug 20 12:04:33 2014
;; MSG SIZE  rcvd: 172
 
C:\>dig -taaaa www.comcast.net @75.75.76.76
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @75.75.76.76
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60823
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.comcast.net.               IN      AAAA
 
;; ANSWER SECTION:
www.comcast.net.        51      IN      CNAME   www.comcast.net.edgesuite.net.
www.comcast.net.edgesuite.net. 280 IN   CNAME   a1526.dscg.akamai.net.
a1526.dscg.akamai.net.  20      IN      AAAA    2600:1404:a::1743:fc08
a1526.dscg.akamai.net.  20      IN      AAAA    2600:1404:a::1743:fc19
 
;; Query time: 46 msec
;; SERVER: 75.75.76.76#53(75.75.76.76)
;; WHEN: Wed Aug 20 12:04:56 2014
;; MSG SIZE  rcvd: 172
 

camper
just visiting this planet
Premium Member
join:2010-03-21
Bethel, CT

camper to mb6

Premium Member

to mb6
 
For me, it looks like FEED::1 is in Boston, and FEED::2 is in Pittsburgh. Both are responding fine, though I usually do not use Comcast's DNS due to past unreliability.

depster
join:2001-06-07
Grand Rapids, MI

depster to SLC 96

Member

to SLC 96

Re: [IPv6] Re: Comcast IPv6 DNS server down

The Chicago IPV6 DNS server appears to be back up and running.


3 10 ms 10 ms 9 ms sur03.grandrapids.mi.michigan.comcast.net [2001:558:110:0:c000::4]
4 17 ms 16 ms 15 ms te-0-0-0-7-ar01.taylor.mi.michigan.comcast.net [2001:558:110:200b::1]
5 15 ms 14 ms 15 ms te-0-8-0-10-ar01.pontiac.mi.michigan.comcast.net [2001:558:110:5005::2]
6 26 ms 24 ms 26 ms he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f6b7::1]
7 25 ms 23 ms 27 ms pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net [2001:558:0:f600::2]
8 21 ms 23 ms 24 ms te-9-1-ur09-d.area4.il.chicago.comcast.net [2001:558:300:52::1]
9 23 ms 24 ms 22 ms te-8-1-ur08-d.area4.il.chicago.comcast.net [2001:558:300:53::1]
10 22 ms 21 ms 23 ms te-9-4-ur05-d.area4.il.chicago.comcast.net [2001:558:300:e8::1]
11 24 ms 23 ms 24 ms cdns01.comcast.net [2001:558:feed::1]

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

NetFixer

Premium Member

said by depster:

The Chicago IPV6 DNS server appears to be back up and running.

Yep, not only responding to traceroute and pings, but it actually answers DNS queries again:

X:\>dig -taaaa www.comcast.net @2001:558:feed::1
 
; <<>> DiG 9.9.2 <<>> -taaaa www.comcast.net @2001:558:feed::1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39117
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.comcast.net.               IN      AAAA
 
;; ANSWER SECTION:
www.comcast.net.        85      IN      CNAME   www.comcast.net.edgesuite.net.
www.comcast.net.edgesuite.net. 59 IN    CNAME   a1526.dscg.akamai.net.
a1526.dscg.akamai.net.  13      IN      AAAA    2600:1402:e::b833:9698
a1526.dscg.akamai.net.  13      IN      AAAA    2600:1402:e::b833:96a0
 
;; Query time: 46 msec
;; SERVER: 2001:558:feed::1#53(2001:558:feed::1)
;; WHEN: Wed Aug 20 20:18:20 2014
;; MSG SIZE  rcvd: 172