Help with Network Configuration

imranpanji said:
That confirms my point, that running your own DNS server, pointing to the root servers, you will still get content from the local servers, as his public IP address is within the SA netblocks.
Click to expand...
Not that simple or cut & dry.

For ISPs with which they have no commercial relationship, Akamai build a geolocation netblock database probably derived from live BGP & other sources. However for their partners/customers, the ones who actually host Akamai caches, the netblocks are specified, and these may not include the entire address space (specifically user allocated).

So it will be hit & miss depending on ISP being used. The only way to guarantee you resolve the most optimal content location (if available), is to use your ISP's prescribed DNS servers, e.g.

C:\>ping download.microsoft.com

Pinging a767.ms.akamai.net [197.80.130.11] with 32 bytes of data:
Reply from 197.80.130.11: bytes=32 time=9ms TTL=59
Reply from 197.80.130.11: bytes=32 time=9ms TTL=59
Reply from 197.80.130.11: bytes=32 time=9ms TTL=59
Reply from 197.80.130.11: bytes=32 time=9ms TTL=59

Ping statistics for 197.80.130.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms
 
Last edited:
So with the Google public DNS servers? Is that entirely US centric? How would that work?

What i have noticed after googling this the last few days is that no one is 100% sure of how it works, nearly all the articles that have been written on this have been 'I think' , or 'it should work like this' . all very confusing
 
imranpanji said:
So with the Google public DNS servers? Is that entirely US centric? How would that work?
Click to expand...
Not so well, flipped my DNS servers to Google (same PC as above ping). This time instead of identifying my ISP, the resolution falls back to closest geolocated 'general' cache, the EU one ...

C:\>ping download.microsoft.com

Pinging a767.ms.akamai.net [95.101.0.89] with 32 bytes of data:
Reply from 95.101.0.89: bytes=32 time=197ms TTL=51
Reply from 95.101.0.89: bytes=32 time=199ms TTL=51
Reply from 95.101.0.89: bytes=32 time=197ms TTL=51
Reply from 95.101.0.89: bytes=32 time=196ms TTL=51

Ping statistics for 95.101.0.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 196ms, Maximum = 199ms, Average = 197ms

imranpanji said:
all very confusing
Click to expand...
Not if you actually start using/testing it, instead of goggling other people's confusion.
 
There are actually Google DNS servers hosted in London, as well as multiple ones in the US. So using Google DNS servers will direct you to akamai caches in london, still slower than the local ones.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X