A simple change to make your website #IPv6 ready.
Making your website accessible by both IPv4 (What everyone is familiar with) and IPv6, those wierd long IP addresses with hex numbers in them, is as simple as
(1) finding your IPv6 address, which you can do by doing a IPConfig /all on your desktop
And getting the IPv6 address from the “6TO4 adapter”
Tunnel adapter 6TO4 Adapter:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:5f9a:f46a::5f9a:f46a(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::1
DHCPv6 IAID . . . . . . . . . . . : 469762048
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-42-14-1B-00-25-90-1E-04-94
(2) Then adding a DNS entry for an AAAA record pointing to the IPv6 address that you found above.
I doubt it will make much difference today or tomorrow, since IPv4 will take a long long time to die out completely, but slowly, IPv6 will become the norm, and it’s best to be ahead of the curve, rather than being behind it.
Network Programming in .NET 