iansltx
join:2007-02-19
Golden, CO
kudos:2 Reviews:
 ·Comcast
| reply to espaeth
Re: [Connectivity] ibone vs cbone The cool thing is, the DNS servers I'm using (4.2.2.x) are actually physically close to where I am, maybe 2-4 ms from my cable node. If I go to DoxPara, it lists different IP addresses for my DNS server, so I think it's effectively forwarding to one in Denver, so DNS Akamai geolocation works. |
|
 espaethDigital PlumberPremium,MVM
join:2001-04-21
Minneapolis, MN
kudos:2
 ·Clear Wireless
| said by iansltx:The cool thing is, the DNS servers I'm using (4.2.2.x) are actually physically close to where I am, maybe 2-4 ms from my cable node. The server may be physically close, but like the OpenDNS pools each server is not an independent cache -- they have a caching hierarchy within themselves before they start to query the outside.
So that Level(3) server nice and close to you might actually pull the results from an central cache in Washington DC or San Jose rather than making the external queries directly. |
|
iansltx
join:2007-02-19
Golden, CO
kudos:2 Reviews:
·Comcast
| I'm following. Seems like a rather broken system Akamai is using, since DNS servers can cache and do all sorts of odd stuff.
Anyone know what the default DNS servers for Comcast are in the Denver area, and what their location is? On the Level3 DNS servers, it appears as though I'm now being routed to Dallas via Level3 for Akamai stuff. Better...but not perfect if Akamai actually has COmcast-accessible servers in the area. |
|
|
|
iansltx
join:2007-02-19
Golden, CO
kudos:2 Reviews:
·Comcast
| Hmm, seem to have found dns.cmc.co.denver.comcast.net. Any others? I case you're wondering, yes this did dramatically decrease Akamai pings, but nothing else as far as I can tell. It's not like 3ms of NS resolution is going to make things faster unless the resolution is to a totally different server... |
|
