|
Google to convert YouTube to IPv6
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 23 November 2009 14:05:38
Google to convert YouTube to IPv6
![[be]](/s/countries/be.gif) Shadow Hawkins on Friday, 29 January 2010 18:24:50
This is done as of today (or yesterday), Erik Kline (of Google) has announced it on some lists and at the Networkers conference.
A really good news as youtube is not a small part of Internet traffic.
Google to convert YouTube to IPv6
![[ro]](/s/countries/ro.gif) Shadow Hawkins on Thursday, 04 February 2010 23:03:42
Yes, according to this, some selected networks receive both IPv4 and IPv6 addresses when querying for www.youtube.com. As I understand, it depends on the resolver you are querying.
Any chance nscache.{eu,us,ap}.sixxs.net will do this?
Google to convert YouTube to IPv6
Yes, already since April 2009 ;)
The only requirement for "Google IPv6" is that one has IPv6 connectivity and that one uses a DNS resolver which is whitelisted, thus using our Recursive DNS Cache Service will do that just fine.
Google to convert YouTube to IPv6
Shadow Hawkins on Friday, 05 February 2010 09:43:38
Heh, I was confused by dig. The guy in the link was using host which seems to return, by default, both A and AAAA records, while dig defaults to A.
user@homepc:~$ dig www.youtube.com @nscache.eu.sixxs.net
; <<>> DiG 9.6.1-P2 <<>> www.youtube.com @nscache.eu.sixxs.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13153
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.youtube.com.INA
;; ANSWER SECTION:
www.youtube.com.48980INCNAMEyoutube-ui.l.google.com.
youtube-ui.l.google.com. 300INA74.125.87.101
youtube-ui.l.google.com. 300INA74.125.87.138
youtube-ui.l.google.com. 300INA74.125.87.113
youtube-ui.l.google.com. 300INA74.125.87.100
youtube-ui.l.google.com. 300INA74.125.87.102
;; Query time: 133 msec
;; SERVER: 2001:1418:10:2::2#53(2001:1418:10:2::2)
;; WHEN: Fri Feb 5 10:41:40 2010
;; MSG SIZE rcvd: 147
user@homepc:~$ dig AAAA www.youtube.com @nscache.eu.sixxs.net
; <<>> DiG 9.6.1-P2 <<>> AAAA www.youtube.com @nscache.eu.sixxs.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5931
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.youtube.com.INAAAA
;; ANSWER SECTION:
www.youtube.com.48926INCNAMEyoutube-ui.l.google.com.
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::71
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::8b
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::8a
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::65
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::64
youtube-ui.l.google.com. 282INAAAA2a00:1450:8007::66
;; Query time: 130 msec
;; SERVER: 2001:1418:10:2::2#53(2001:1418:10:2::2)
;; WHEN: Fri Feb 5 10:42:33 2010
;; MSG SIZE rcvd: 235
user@homepc:~$ host www.youtube.com nscache.eu.sixxs.net
Using domain server:
Name: nscache.eu.sixxs.net
Address: 2001:1418:10:2::2#53
Aliases:
www.youtube.com is an alias for youtube-ui.l.google.com.
youtube-ui.l.google.com has address 74.125.87.101
youtube-ui.l.google.com has address 74.125.87.138
youtube-ui.l.google.com has address 74.125.87.100
youtube-ui.l.google.com has address 74.125.87.113
youtube-ui.l.google.com has address 74.125.87.102
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::64
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::66
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::65
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::71
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::8b
youtube-ui.l.google.com has IPv6 address 2a00:1450:8007::8a
Hence my confusion.
Google to convert YouTube to IPv6
Shadow Hawkins on Friday, 05 February 2010 05:28:50
Sweet! I've been viewing YouTube over IPv6 and didn't know it. It sure makes a mess of "netstat -an", though.
C:\Users\[accountname]>ping www.youtube.com
Pinging youtube-ui.l.google.com [2001:4860:8006::8b] with 32 bytes of data:
Reply from 2001:4860:8006::8b: time=77ms
Reply from 2001:4860:8006::8b: time=78ms
Reply from 2001:4860:8006::8b: time=78ms
Reply from 2001:4860:8006::8b: time=78ms
Ping statistics for 2001:4860:8006::8b:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms
|
![[ch]](/s/countries/ch.gif)
on Friday, 05 February 2010 01:11:33
Posting is only allowed when you are