Coming up on October 8, 2013, we will be running our IPv6: Understanding, Analysis & Implementation training course here at our Virginia Beach facility. Let’s face it, the implementation of IPv6 is inevitable and will effect every enterprise network on the planet eventually. The protocol is already being deployed worldwide! IPv6 allows for increased address […]
We spotted this interesting IPv6 article this morning written by Angus Kidman at Lifehacker and wanted to share it with you. Here’s an excerpt: “We’ve known for decades that the available pool of IPv4 address was eventually going to dry up, but despite numerous warnings usage of its successor IPv6 is still minimal. Why haven’t […]
Most DNS servers these days are glad to resolve IPv6 addresses from clients who send the queries packaged in IPv4 packets. In the grand scheme of things the DNS servers don’t care how you sent the question, they just care about the question. And because almost everybody still relies heavily upon IPv4, most of us who are trying to push toward IPv6 have been satisfied to get our AAAA resolutions using IPv4 as the transport. But if you want to start being more ‘pure’ in your IPv6 deployments you need to give your system the ability to not only send IPv6 packets out into the Internet, you also need to learn where it is you are going via IPv6 as well. Put plainly, you need to configure your system to get its IPv6 name resolution using IPv6 packets.
One very cool and highly promoted feature of IPv6 is stateless address autoconfiguration. If you don’t already know, this feature enables a node to automatically derive its IPv6 address(es) without the help of of a DHCP server. That is a big departure from the world of IPv4. In IPv4 you either had to manually configure your IP addresses or you had to use DHCP. IPv6 has added address autoconfiguration as a third (and typically default) option.