TKJunkMail
Enjoy the sun
Premium
join:2002-03-03
Avalon, NJ
 ·Sprint Mobile Broa..
 ·Comcast
| reply to Morty
Re: [DNS] DNS Outage is Resolved - Please Read
said by Morty  :When Setting your DNS Statically, set the Primary DNS server to one of the two Comcast National DNS server: 68.87.66.196(Colorado), 68.87.64.196(Pa) and set the secondary DNS server to one of your choice. Here a couple pics on how to do this in a router(netgear) and in win xp/sp2:
However I made my primary the Verizon DNS in NYC since it is closest to NJ. |
|
rseiler
join:2001-11-01
1 edit | said by TKJunkMail
However I made my primary the Verizon DNS in NYC since it is closest to NJ.
You mean 4.2.2.1? That appears to be in Broomfield, CO. |
|
TKJunkMail
Enjoy the sun
Premium
join:2002-03-03
Avalon, NJ
·Sprint Mobile Broa..
·Comcast
| said by rseiler :You mean 4.2.2.1? That appears to be in Broomfield, CO. I used 4.2.2.4 and 4.2.2.6 which tracert shows as being in NYC.
5 12.118.114.9 16ms 17ms 15ms TTL: 0 (No rDNS)
6 12.123.137.62 20ms 16ms 19ms TTL: 0 (tbr1-p012301.phlpa.ip.att.net probable b
*ogus rDNS: No DNS)
7 12.122.2.17 58ms 20ms 17ms TTL: 0 (tbr1-cl8.n54ny.ip.att.net probable bogus
* rDNS: No DNS)
8 12.123.3.105 33ms 17ms 15ms TTL: 0 (ggr2-p310.n54ny.ip.att.net probable bogu
*s rDNS: No DNS)
9 209.244.160.129 20ms 17ms 16ms TTL: 0 (so-0-2-0.gar4.NewYork1.Level3.net ok)
10 4.68.97.168 17ms 29ms 16ms TTL: 0 (ge-5-2.core1.NewYork1.Level3.net ok)
11 4.2.2.4 17ms 19ms 18ms TTL:245 (vnsc-pri-dsl.genuity.net ok)
(*) WARNING 3 long line(s) split
5 12.118.114.9 27ms 15ms 19ms TTL: 0 (No rDNS)
6 12.123.137.62 17ms 17ms 19ms TTL: 0 (tbr1-p012301.phlpa.ip.att.net probable b
*ogus rDNS: No DNS)
7 12.122.2.17 19ms 17ms 50ms TTL: 0 (tbr1-cl8.n54ny.ip.att.net probable bogus
* rDNS: No DNS)
8 12.123.3.58 16ms 17ms 17ms TTL: 0 (ggr2-p300.n54ny.ip.att.net probable bogu
*s rDNS: No DNS)
9 209.244.160.129 26ms 18ms 18ms TTL: 0 (so-0-2-0.gar4.NewYork1.Level3.net ok)
10 4.68.97.72 30ms 15ms 15ms TTL: 0 (ge-2-1.core1.NewYork1.Level3.net ok)
11 4.2.2.6 16ms 33ms 18ms TTL:245 (vnsc-lc-dsl.genuity.net ok)
(*) WARNING 3 long line(s) split |
|
rseiler
join:2001-11-01
| said by TKJunkMail :I used 4.2.2.4 and 4.2.2.6 which tracert shows as being in NYC. This is interesting. I'm in the Northwest, so the route is far different:
8 31 ms 31 ms 32 ms tbr2-p013701.sffca.ip.att.net [12.123.13.177]
9 33 ms 32 ms 34 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
10 31 ms 30 ms 32 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
11 51 ms 51 ms 43 ms so-1-2-0.bbr1.SanJose1.Level3.net [209.244.3.137]
12 31 ms 55 ms 31 ms ge-10-0.core1.SanJose1.Level3.net [4.68.123.6]
13 57 ms 53 ms 79 ms vnsc-pri-dsl.genuity.net [4.2.2.4]
8 32 ms 30 ms 51 ms tbr2-p013701.sffca.ip.att.net [12.123.13.177]
9 40 ms 42 ms 54 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
10 32 ms 32 ms 31 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
11 * 32 ms 36 ms so-1-2-0.bbr1.SanJose1.Level3.net [209.244.3.137]
12 36 ms 32 ms 54 ms ge-11-0.core1.SanJose1.Level3.net [4.68.123.102]
13 33 ms 33 ms 31 ms vnsc-lc-dsl.genuity.net [4.2.2.6]
Now, from these it appears that they're in the Bay Area. Yet with yours it appears that they're in NYC. It can't be both, but I think neither. Why? Because I'm using VisualRoute, a program that maps the route, and the last hop bounces to Colorado from the Bay Area, something that plain traceroute doesn't show. I suspect if you ran it, the last hop would bounce from NYC to the same place. |
|
kjstone00
 from:
TKJunkMail
| Most, if not all, large providers use a technique called anycast. There are many physical servers located all over the provider network and all answer to the same set of ip addresses.
This makes user side setup and troubleshooting easier and provides failover as well.
Your DNS requests will go to the closest server to you, if available, and others if necessary.
Something dramatic happened on the Comcast network to cause a failure of this scale. I would find it unlikely that the same set of circumstances would be allowed to happen again. |
|
