Forum - Google & IPv6 :: SixXS - IPv6 Deployment & Tunnel Broker

Google & IPv6

Shadow Hawkins on Thursday, 08 January 2009 15:48:18

Perhaps the announcement from Google this week is something for SixXS ? Cheers, Bart

Google & IPv6

Jeroen Massar SixXS Staff

on Thursday, 08 January 2009 16:25:13

Check the About Page and you might get an idea who is working where to get a small hint. As for the slashdot article, lets see how good the Editors there really read (they don't do spellchecking it seems, oopsy ;) it and if they notice the last tiny ref to the article from nearly 6 years ago also asking the same question.

Google & IPv6

Shadow Hawkins on Thursday, 08 January 2009 19:48:01

It's not clear to me that this would affect IPv6 tunnels. As far as I know, SixXS does not run resolvers for us. In my case I am running my own resolver on my home network with my ISP's resolver as a backup. Surely my IPv4-only ISP resolver won't be using this. And I don't think any IPv4-transported DNS requests from my home resolver would be able to use this. But if my home resolver attempts IPv6-transported lookups will I be able to use Google over IPv6 with my SixXS tunnel? Alternately, since I do run my own resolvers I could selectively forward zone requests to specified servers. Is there a Google DNS server I can point to for AAAA records for google.com zones? I will make the effort to use IPv6 services wherever I can to help show that some people are trying to use it.

Google & IPv6

Shadow Hawkins on Thursday, 08 January 2009 20:12:31

I don't know of any DNS servers; I'm just hacking my hosts file to point all Google traffic to their IPv6 address at 2001:4860:0:2001::68 I haven't had any problems with it (except when my tunnel is down)

Google & IPv6

Carmen Sandiego on Tuesday, 13 January 2009 15:34:53

2001:4860:0:2001::68 seems to be in US somewhere (at least ping is > 100 ms as seen from my box). EU users might like to try 2001:4860:0:1001::68 instead. Cheers.

Google & IPv6

Shadow Hawkins on Thursday, 08 January 2009 21:15:22

Maybe sixxs could ask google to enable AAAA responses when query is going from _any_ sixxs assigned IPv6? That should work.

Google & IPv6

Shadow Hawkins on Friday, 09 January 2009 08:31:56

The Problem is that most probably the requests from most tunnel users will go to their ISP, which ist not v6 enabled, which in turn will ask google to resolve the queries, and in turn will get only an A record for google sites. For google there is no way to see that the request originated from a sixxs user. But I'm sure that if more companies will go v6 enabled in the way google does there quickly will be suitable nameservers reachable... ;-)

Google & IPv6

Shadow Hawkins on Friday, 09 January 2009 12:55:37

The AAAA are served based on the source-ip of the DNS server. As your DNS server doesn't get set, when you establish a tunnel, you are still using the DNS server that your IPv4 ISP supplied you with. Also, SixXS can not apply to get it done for any SixXS PoP easily, because they are all different ISPs. What could be done is to set up a couple of DNS servers, that allow recursion (maybe with IPv6 access only) and then ask Google to enable them for AAAA records.

Google & IPv6

Shadow Hawkins on Wednesday, 14 January 2009 21:00:02

Unfortunately none of Google's DNS servers are v6-enabled so you cannot get to google from a v6-only network.

Google & IPv6

Shadow Hawkins on Tuesday, 20 January 2009 00:14:10

I was also thinging about that and I have created a custom backend for powerdns that append aaaa recors for google. My custom dns server is at 2001:470:9971:1001::53 - it's recursive - so far only add aaaa record (invalid one for now) for google.fi and www.google.fi - the speed needs improvement - much more google domains and real ips soon Simple check: dig @2001:470:9971:1001::53 www.google.fi dig @2001:470:9971:1001::53 aaaa www.google.fi Take care, Piotr J.

Google & IPv6

Shadow Hawkins on Friday, 09 January 2009 06:49:40

Well, IPv6 AAAA-resolution works in Server 2003, 2008, BIND, and I think MaraDNS, so at the very least we subnet operators can operate our own DNS servers that are AAAA compliant (the ones for my company are). I have lobbed queries with OpenDNS for IPv6 support as well.

Google & IPv6

Shadow Hawkins on Friday, 09 January 2009 13:07:54

PowerDNS works, too.

Google & IPv6

Shadow Hawkins on Sunday, 18 January 2009 05:21:25

I came across this. If you have Vista, 2008, or 7, you can set specific IPv6 DNS servers. I'm currently using the addresses for ns1.sixxs.net and one of my work DNS servers. I would suggest people who know the right people nudge them to post AAAA addresses for public DNS servers. https://www.sixxs.net/forum/?msg=setup-31491

Google & IPv6

Jeroen Massar SixXS Staff

on Sunday, 18 January 2009 08:36:31

That message was from 2003. That has changed a long time ago and ns{1|2|3}.sixxs.net are authoritive only and don't do recursive queries:

jeroen@abaddon:~$ dig @ns1.sixxs.net www.microsoft.com ; <<>> DiG 9.5.0-P2 <<>> @ns1.sixxs.net www.microsoft.com ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 21628 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available [..] jeroen@abaddon:~$ dig @ns2.sixxs.net www.microsoft.com ; <<>> DiG 9.5.0-P2 <<>> @ns2.sixxs.net www.microsoft.com ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29961 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13 ;; WARNING: recursion requested but not available [..] ; <<>> DiG 9.5.0-P2 <<>> @ns3.sixxs.net www.microsoft.com ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 16157 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.microsoft.com. IN A [..]

Google & IPv6

Shadow Hawkins on Sunday, 15 February 2009 07:17:34

I created my own server here at my house to route queries from. I did find an auto-generated list of IPv6 rDNS servers at he.net: most of them are commercial servers or specific networks. College users (edu sites) could use their IPv6 DNS servers. This is extremely hit or miss though. I can't wait until OpenDNS goes V6. http://bgp.he.net/ipv6-progress-report.cgi

Please note Posting is only allowed when you are logged in.