On 05/18/12 12:51 am, Dave Yeo thus wrote :
I suspect they will for some time. Also, it's really a DNS thing. As
long as your uplevel DNS server responds to an IPv4 query with IPv4
info, you shouldn't have a problem. In 2005, I filed the following bug
while in Dresden at the OS/2 Developers Conference and experiencing
difficulties with FF:
https://bugzilla.mozilla.org/show_bug.cgi?id=300302
To clarify the above statement, an IPv6 DNS server which is listening on
an IPv4 IP (dual stack) should properly respond to an IPv4 request (an
IPv4 client will never request resolution of an AAAA record, as no such
animal exists in the IPv4 universe; it would be kind of like a resident
in Flatland asking how high a building was). The important thing is that
the DNS server is listening and responding on/to an IPv4 address, and
will continue to provide IPv4 data.
To get an idea of IPv6 adoption (and conversely, IPv4 orphaning), one
might want to check out
http://mnlab-ipv6.seas.upenn.edu:8080/monitor/
or one of the linked monitors from there.
The mechanism used to translate between IPv4 & IPv6 is called NAT-PT
(Network Address Translation-Protocol Translation) and is defined in RFC
2677(?) (yes; just re-checked). NAT-PT is the/an alternative to running
both stacks simultaneously, though surely not ideal (and, unless you
have *something* local which understands both protocols, this isn't
going to be feasible).
So, when the time comes that you bump into a regular situation, Dave,
where you can't access one or more important sites because it/they
has/have *no* IPv4 address (or perhaps it does/they do but for whatever
reason, no A record(s) exist), then you can look into putting something
else between you and the internet to do the translation.
An excellent reference for all things IPv6 is
http://ipv6.com.