|
"open" IPV6-resolvers for google
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Wednesday, 11 August 2010 13:40:32
As google only discloses ipv6-adresses to ipv6-approved dns-servers, I see google via ipv4.
Are there ipv6-approved dns-servers, I could point my dns-server to to get ipv6-adresses for google and youtube?
I'm in Denmark, but heck, if I got a server in US, I might be able to see those "not approved outside USA"-videos on youtube :-)
"open" IPV6-resolvers for google
"open" IPV6-resolvers for google
![[de]](/s/countries/de.gif) Carmen Sandiego on Wednesday, 18 August 2010 14:19:51
I solved it in another way. I set up my own free dns server and made a zone file for ipv6.google.com and it works flawlesly on bind 9.
fiel name: ipv6.google.com.zone
zone file:
$TTL 900
@ IN SOA ns3.google.com. dns-admin.google.com. (
[.. ADMIN REMOVED as this will only break your setup..]
Mybe this configuration will help others too
"open" IPV6-resolvers for google
Shadow Hawkins on Monday, 16 August 2010 15:19:56
A: This does't seem to give an ipv6-addr for google.com
B: Ip-adresses are known to change. When google moves servers your setup may break.
But as long as it's your own servers or clients, that break...
Leif
"open" IPV6-resolvers for google
You do realize that ipv6.google.com is ALWAYS giving you AAAA addresses right?
The cool thing about the recursive DNS servers is that they do that for www.google.com, maps.google.com, youtube and various other google services...
"open" IPV6-resolvers for google
Shadow Hawkins on Wednesday, 18 August 2010 14:35:20The cool thing about the recursive DNS servers is that they do that for www.google.com, maps.google.com, youtube and various other google services...
I haven't been able to determine if the recursive servers are censored or give the true adresses for stuff like piratebay and russian mp3-sellers :-)
"open" IPV6-resolvers for google
The only thing where the SixXS DNS servers are special is that they are in the approved google and wikipedia leaks, thus get IPv6 addresses from there. For the rest they don't do anything else, no logs, no changes whatsoever.
We are not the judges on what is 'illegal' or not as we are not the government.
Of course, that is different from hosting illegal stuff on a SixXS endpoint, then we will take action when we are requested to do so and the request is valid, but that concerns connectivity, not the DNS caches.
"open" IPV6-resolvers for google
Carmen Sandiego on Wednesday, 18 August 2010 14:20:06
here is another one I tried out and it works...
google.com.zone
google.com. 84874 IN SOA ns3.google.com. dns-admin.google.com. (
[.. ADMIN REMOVED as this will only break your setup..]
I'm testing every day because I have an own free dns server with ipv6 support
ipv4 and ipv6 address
"open" IPV6-resolvers for google
I've removed your long dumps of made up zonefiles as that is really not how one should approach this problem.
If you want to use the IPv6 variant of Google's services, either use one of the many DNS recursors that provide you with proper information or just don't.
If you are going to locally hard code these zone files then you will get suboptimal routing and most likely broken connectivity, next to the fact that you are missing a lot of other IPv6 enabled domains that Google has enabled with more and more following.
"open" IPV6-resolvers for google
Shadow Hawkins on Wednesday, 18 August 2010 14:39:08
Have anybody tried to get "google-approval" for their own recursive nameservers?
I wonder if google will accept "I know it will work for our private network, so don't worry"
Leif
"open" IPV6-resolvers for google
Try ipv6@google.com
But from their FAQ, no they don't.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 11 August 2010 14:48:45
Posting is only allowed when you are