----- Original Message -----

From: "John Orthoefer" <jco@direwolf.com>

I see those guys at BBNPlanet is trying to compete with them using 4.2.2.1, .2, and .3.

C'mon, John; no trolling. :-) Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274

not bad for CDNs anymore: http://arstechnica.com/telecom/news/2011/08/opendns-and-google-working-with-... t On Mon, Oct 10, 2011 at 5:45 PM, Scott Howard <scott@doc.net.au> wrote:

This service has been discussed several times in the ~2 years since it was first released (including topics such as why it's bad for CDNs)

The archives would be a good place to start...

 Scott.

On Mon, Oct 10, 2011 at 2:12 PM, steve pirk [egrep] <steve@pirk.com> wrote:

...

I saw this in a post from Travis Wise of Google yesterday. Pretty cool for those users who do not want to use their ISP's name servers, or just want to have dns resolve quickly from anywhere in the world. In either case, I think it is cool ;-]

http://code.google.com/speed/public-dns/

Here is the original post - Yes, this one is public... oops! https://plus.google.com/111937447827665620879/posts/27S6QB8j1Ry

Nice easy numbers to remember too. 8.8.8.8 and 8.8.4.4

-- steve pirk yensid "father... the sleeper has awakened..." paul atreides - dune kexp.org member august '09

Wow, consider me educated on old news. LOL I imagine it is new to many of the users on the new service they launched. I completely forgot that Nanog would probably be the first to comment and chime in when it first became available. Thanks for the information. I will definitely research the CDN issues. Back to school steve...Why did I Awesome link Todd - Why did I think that the resolving server would already know "where network path wise" the request came from. Let me post this as a comment and ask how the CDN endpoint routing is working. Better yet, change the dns on my router, and Netflix on the Google TV should let me know how well it is streaming. --steve On Mon, Oct 10, 2011 at 15:10, Michael Painter <tvhawaii@shaka.com> wrote:

Todd Underwood wrote:

...

not bad for CDNs anymore:

http://arstechnica.com/**telecom/news/2011/08/opendns-** and-google-working-with-cdns-**on-dns-speedup.ars<http://arstechnica.com/telecom/news/2011/08/opendns-and-google-working-with-cdns-on-dns-speedup.ars>

t

Fwiw, ol' Steve Gibson has written a small (167KB), .exe, "DNS Benchmark". It's easy to add 8.8.8.8 and 8.8.8.4 (or any nameserver) to the .ini file from within the program . http://www.grc.com/dns/**benchmark.htm<http://www.grc.com/dns/benchmark.htm> --Michael

-- steve pirk yensid "father... the sleeper has awakened..." paul atreides - dune kexp.org member august '09 - Google+ pirk.com

On Tue, Oct 11, 2011 at 1:19 AM, Scott Howard <scott@doc.net.au> wrote:

the initial release date (not actually shown in the that version as far as I can see, but it was around the same time Google announced their public DNS servers).

jan 27 2011, so says the doc header...

At 22-07-2011 20:59, Michael Painter wrote:

Fwiw, ol' Steve Gibson has written a small (167KB), .exe, "DNS Benchmark". It's easy to add 8.8.8.8 and 8.8.8.4 (or any nameserver) to the .ini file from within the program . http://www.grc.com/dns/benchmark.htm --Michael

There's also namebench, does a lot of more tests, and runs at Mac OSX and Linux too: http://code.google.com/p/namebench/

At 11-10-2011 10:58, Michael Painter wrote:

Interesting choice of URLs.

I wonder how many folks are wasting their time chasing this ominous sounding a.. www.paypal.com is hijacked: 173.0.88.34, 173.0.84.2, 173.0.84.34, 173.0.88.2

--Michael

I guess you selected the Alexa top1000 as data-source, which contains this selection of URLs. The result of mis-matching IP addresses reports could be the result of geo-dns, serving different results to different parts of the world to match local CDN nodes.