In message <SNT119-W21F584CCDCDE1F6448EFDADC2C0@phx.gbl>, Brandon Kim writes:
Jens:
There some ISP's trying to push IPv6. Probably not until the masses really = demand it in someway. Or if Google pushes it or some well known company. Perhaps maybe an applica= tion that is IPv6 specific....
Google is pushing it. The problem is the brower vendors still don't support multi-homed sites well despite it being in host requirements for 20+ years. IPv4 + IPv6 give you a multi-homed site. If you have IPv6 connectivity then you can get to google over IPv6, they will even return AAAA records if you register with them. See the browser problem above for why they are taking this route. Mark
dig google.com aaaa
; <<>> DiG 9.3.2 <<>> google.com aaaa ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54613 ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;google.com. IN AAAA ;; ANSWER SECTION: google.com. 300 IN AAAA 2a00:1450:8006::67 google.com. 300 IN AAAA 2a00:1450:8006::68 google.com. 300 IN AAAA 2a00:1450:8006::69 google.com. 300 IN AAAA 2a00:1450:8006::6a google.com. 300 IN AAAA 2a00:1450:8006::93 google.com. 300 IN AAAA 2a00:1450:8006::63 ;; AUTHORITY SECTION: google.com. 235307 IN NS ns2.google.com. google.com. 235307 IN NS ns3.google.com. google.com. 235307 IN NS ns4.google.com. google.com. 235307 IN NS ns1.google.com. ;; ADDITIONAL SECTION: ns1.google.com. 59146 IN A 216.239.32.10 ns2.google.com. 65481 IN A 216.239.34.10 ns3.google.com. 59146 IN A 216.239.36.10 ns4.google.com. 59146 IN A 216.239.38.10 ;; Query time: 30 msec ;; SERVER: 204.152.184.67#53(204.152.184.67) ;; WHEN: Thu Mar 18 00:08:37 2010 ;; MSG SIZE rcvd: 332
NAT's and transition protocols seems to extend the life of IPv4. I'm not ag= ainst them though=2C they have served us well....hard to let go of things that worked for you for so many years..= ..
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org