news from Google

Hi,

now Google DNS, anything more?

http://googlecode.blogspot.com/2009/12/introducing-google-public-dns-new-dns.html

Eduardo.-

now Google DNS, anything more?

GoogleNation.

Cheers
Jorge

8.8.8.8 .... 6.6.6.6 would have been really really funny. :slight_smile:

Jorge Amodio wrote:

now Google DNS, anything more?

GoogleNation.

No kiddng. I must be the only one who is getting tired of seeing Google
take over literally everything.

~Seth

GoogleWave?

Regards,

Xavier

Excerpts from Charles Wyble's message of Thu Dec 03 10:44:49 -0800 2009:

8.8.8.8 .... 6.6.6.6 would have been really really funny. :slight_smile:

Nice IPs from Level 3, huh?

6.6.6.6 belongs to the US Army.

--j

uf, another question I'll have ask my users now:

User: I can't get to the intranet.mycompanydomain.local! What did you
break!?
Me: Hey, you can't to the intranet,domain.local? Did you make your laptop
use Google DNS?

For sure...everyone remembers the Bill Gates Borg picture, but at this
rate, Google will soon become the new poster child for that picture (or
something comparable).

Bret

For sure...everyone remembers the Bill Gates Borg picture, but at this
rate, Google will soon become the new poster child for that picture (or
something comparable).

Bret

I try to think of them as a benevolent dictator :wink:

-brandon

uf, another question I'll have ask my users now:

User: I can't get to the intranet.mycompanydomain.local! What did you
break!?
Me: Hey, you can't to the intranet,domain.local? Did you make your laptop
use Google DNS?

1) If $COMPANY does not force their VPN client to disallow external DNS, shame on them.

2) You already have this issue. Google is hardly the first, and no where near the biggest (nor will they be in all likelihood, despite their name).

3) I know, none of that matters. You still get phone calls.

4) Welcome to the ISP business.

(Another reason I Am Not An Isp. :slight_smile:

I'm surprised that Google's new DNS service does not return better results
  for google.com than some local DNS resolvers do. My server is in Fairfax,
  VA. Does Google use Anycast'ed IPs or is it still a hybrid of
  split-horizon DNS and other things, as discussed previously:

     http://www.merit.edu/mail.archives/nanog/2009-02/threads.html#00269

  Here's the results from some various DNS servers for Google.com. I
  thought Google had a datacenter in Ashburn, VA, but I'm not getting there.
  Maybe it's gone. Maybe the shortest route doesn't matter anymore.

     --> dig +short google.com @208.67.222.222 # OpenDNS
     74.125.53.100
     74.125.67.100
     74.125.45.100
     --> dig +short google.com @8.8.8.8 # Google DNS
     74.125.67.100
     74.125.53.100
     74.125.45.100
     --> dig +short google.com @8.8.4.4 # Google DNS 2
     74.125.67.100
     74.125.53.100
     74.125.45.100
     --> dig +short google.com @198.6.1.1 # UUNET/Verizon Cache server (cache00.ns.uu.net)
     74.125.53.100
     74.125.67.100
     74.125.45.100
     --> dig +short google.com @198.6.1.2
     74.125.45.100
     74.125.53.100
     74.125.67.100
     --> dig +short google.com @198.6.1.3
     74.125.45.100
     74.125.67.100
     74.125.53.100
     --> dig +short google.com @198.6.1.4
     74.125.45.100
     74.125.53.100
     74.125.67.100
     --> dig +short google.com @198.6.1.5
     74.125.67.100
     74.125.45.100
     74.125.53.100
   * --> dig +short google.com @70.164.18.41 # Nova.org (Small VA ISP) Caching DNS
     74.125.45.100
     74.125.53.100
     74.125.67.100
   * --> dig +short google.com @208.94.147.150 # Tiggee DNS (VA company)
     74.125.45.100
     74.125.67.100
     74.125.53.100

     --> ping -c 10 74.125.45.100
     10 packets transmitted, 10 packets received, 0% packet loss
     round-trip min/avg/max/stddev = 18.079/20.522/25.272/2.200 ms

     --> ping -c 10 74.125.53.100
     10 packets transmitted, 10 packets received, 0% packet loss
     round-trip min/avg/max/stddev = 97.721/101.267/107.770/2.856 ms

     --> ping -c 10 74.125.67.100
     10 packets transmitted, 10 packets received, 0% packet loss
     round-trip min/avg/max/stddev = 97.531/99.238/101.206/1.420 ms

  Only the last two starred DNS records returned what _seems_ to be the best
  result for Google.com. Then again, someone from Google might be able to
  explain the logic behind the results.

  And to rip off the bandaid on the "What DNS Is Not" discussion, Google's
  DNS does return the expected NXDOMAIN for the very small test I did.

I think of this as an obvious (not necessarily beneficial for all, of
course) step for a company which lives out of advertisement - i.e. what if
they could capture your habits for browsing at the FQDN-to-IP time -
wouldn't that add more to their knowledge base?

***Stefan Mititelu
http://twitter.com/netfortius
http://www.linkedin.com/in/netfortius

http://www.collegehumor.com/article:1793643

--bill

I think of this as an obvious (not necessarily beneficial for all, of
course) step for a company which lives out of advertisement - i.e. what if
they could capture your habits for browsing at the FQDN-to-IP time -
wouldn't that add more to their knowledge base?

They have a lot of smart people there trying to provide a good service
and do smart
things, but as they are smart if a large number of users use their
resolvers that's
a lot of juicy statistics that can be monetized in some way.

They will find the way to do it. IMHO.

Jorge

I think of this as an obvious (not necessarily beneficial for all, of
course) step for a company which lives out of advertisement - i.e. what
if
they could capture your habits for browsing at the FQDN-to-IP time -
wouldn't that add more to their knowledge base?

I think there are amazing opportunities to data mine and prevent fraud if you can get a percentage of your users using this.

I'm really excited about the structured attacks that will be run against this thing (cache poisoning... and nastier)... if (for example) when their (or someone's) toolbar is installed, they ask if you'd like to use their "improved" dns service [perhaps they have the whole universe cached to reduce lookup times]. You'd sign up.

And as the wave of software updates proceeds... well, talk about all your eggs in one basket.

Smart ISPs will have an ACL ready to hijack external DNS requests for their whole network in the (inevitable) event something *bad* happens one day and you need to restore service to your customers faster than they can figure out how to fix it themselves. Just a thought.

Deepak

Stefan wrote:

I think of this as an obvious (not necessarily beneficial for all, of
course) step for a company which lives out of advertisement - i.e. what if
they could capture your habits for browsing at the FQDN-to-IP time -
wouldn't that add more to their knowledge base?

I'm certain they will be gathering statistics.

~Seth

Eduardo A. Su�rez wrote:

Hi,

now Google DNS, anything more?

Introducing Google Public DNS: A new DNS resolver from Google - The official Google Code blog

Eduardo.-

yawn. So not interested.

Also reminds me of the Level 3 DNS servers in the 4.2.2.[1-8++] range.

  -Scott

Deepak Jain wrote:

I think there are amazing opportunities to data mine and prevent fraud if you can get a percentage of your users using this.

I'm really excited about the structured attacks that will be run against this thing (cache poisoning... and nastier)... if (for example) when their (or someone's) toolbar is installed, they ask if you'd like to use their "improved" dns service [perhaps they have the whole universe cached to reduce lookup times]. You'd sign up.
  
I agree in a role-reversal method. I think there are amazing methods to
study the correlation and statistical rate of criminal groups and how
they're amassing so much data making things nTimes easier to steal,
spoof and create more frauds. Thanks Google! In fact, because they'd now
have one more tool to work against them, its only a matter of time
before they become smarter (those tinkerers!) That leaves forensics
experts with something to gripe about. Too much of a workload.

Andrey Gordon wrote:

uf, another question I'll have ask my users now:

User: I can't get to the intranet.mycompanydomain.local! What did you
break!?
Me: Hey, you can't to the intranet,domain.local? Did you make your laptop
use Google DNS?

But it is soooo easy to just route 8.8.8.8 and 8.8.4.4 to ISP/enterprise
internal ISP addresses, no more configuration who would have thought of
that...

Greets,
Jeroen