News for hackers. Stuff that matters.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by jbeda on Thursday December 03, 2009 @12:25PM (#974699)
8 is a lucky number. 7.7.7.7 is owned by the US DoD. I love the idea of vanity IP addresses.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by electromagnetic on Thursday December 03, 2009 @01:34PM (#974895)
It's kind of disappointing Google didn't get 1.3.3.7 though.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by Xichekolas on Thursday December 03, 2009 @05:37PM (#975371)
Sadly the 1 block is unallocated, so they would have to make a special request to the IANA to get that address.

Then again, they are Google, so who knows what they could get if they asked...

I'm also curious who Halliburton merged with in order to get the entire 34 block. Surely they weren't around at the time those were handed out so foolishly.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jvdh on Thursday December 03, 2009 @02:18PM (#974992)
Makes me wonder how Google got that subnet though. They really weren't around when those A-nets were being handed out.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by jganetsk on Thursday December 03, 2009 @02:41PM (#975053)
Looks like Level3 owns the 8...* block, and Google must be renting 8.8.8.* and 8.8.4.*.

The DNS service is probably hosted by Level 3.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @04:57PM (#975323)
As with the other story just posted that 4.3.2.1 is a Google DNS server, it also seems to be hosting on Level3.

http://news.ycombinator.com/item?id=975227

Re:Introducing Google Public DNS: A new DNS resolver from Go... by russss on Thursday December 03, 2009 @05:57PM (#975413)
No, the DNS service is run by Google out of their datacenters, they're just renting 8.8.8.0/24 and 8.8.4.0/24 off Level3 because they're memorable numbers.

(It's interesting because 4.2.2.[1-4] are run by Level3)

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jganetsk on Friday December 04, 2009 @12:57AM (#975882)
My problem with posting online is I'm not a clear communicator. I understand that they are renting memorable IP addresses, and I understand that Google is running the DNS service out of the datacenter. I didn't say anything to the contrary.

What I meant by Level3 hosting it is... Level3 is likely the single ISP in front of this service. I don't think Google can get away with multihoming this, other ISPs are just going to push 8.8.8.8 packets to Level3. I don't know how routing tables work, but I don't think they can reliably advertise ownership of the 8.8.8.* block considering it is wholly contained by another block.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by russss on Friday December 04, 2009 @04:21AM (#976043)
No, that's not correct - you can see here that the route is being advertised through no less than 11 intermediate ISPs (and there will be more, that's just from one perspective on the internet):

http://www.ris.ripe.net/cgi-bin/lg/index.cgi?rrc=RRC001&...

They're advertising 8.8.8.0/24, while Level3's route is 8.0.0.0/8 - the more specific route wins.

Google is effectively a tier 1 ISP now, so buying transit off Level3 for those blocks would be a lot more costly than routing them themselves.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jganetsk on Friday December 04, 2009 @11:26AM (#976586)
What do you mean that Google is a tier 1 ISP? Do they provide transit to anyone?

Interestingly, if you can advertise a sub-block and override the bigger block's advertisement, what's stopping people from just stealing sub-blocks from ISPs?

Re:Introducing Google Public DNS: A new DNS resolver from Go... by blasdel on Friday December 04, 2009 @04:38PM (#977259)
> what's stopping people from just stealing sub-blocks from ISPs?

The thief has to either be upstream of your connection, or peered at an extremely high level with others trusting their BGP advertisements. There was a hilarious incident not that long ago where the Pakistanis accidentally blackholed YouTube's IP-block globally (instead of just within the country).

Re:Introducing Google Public DNS: A new DNS resolver from Go... by soundsop on Friday December 04, 2009 @04:12AM (#976039)
Classless inter-domain routing (CIDR) was created exactly for the purpose of freeing up subnets: http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by jganetsk on Friday December 04, 2009 @11:32AM (#976605)
Right, but can you have overlapping blocks? The wikipedia page says nothing about that. It talks about combining smaller blocks to make bigger ones (which is the interesting part). So, if I understand correctly, some routers will see Level3's 8...* advertisement and not Google's 8.8.8.*. They will route 8.8.8.8 to Level3, and that's OK, because Level3 is not going to just drop the packets on the floor. They will forward to Google.

So this is why I said, in my original post, that Level3 is the home of Google's DNS service. If routers are respecting Google's own advertisement, it has to somehow be done with the permission of Level3.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by BerislavLopac on Thursday December 03, 2009 @01:59PM (#974946)
Now imagine what could be done with IPv6 vanity addresses... ;)