On Fri, Feb 4, 2011 at 12:42 PM, <[email protected]> wrote: > Should be able to NAT at the firewall so one could keep internal v4 > addresses. At least, I hope so.
I don't think that will work. 1. Browser is instructed to go www.example.com 2. DNS returns only an IPv6 address record (AAAA) for that site 3. Browser computer has only IPv4 connectivity 4. Now what? The browser cannot plug an IPv6 address into the IPv4 stack. > What a nightmare that could become if > internal needed v6, too. That's what I'm getting at. And really, I don't think it's going to be a nightmare, just a moderate irritation. I see the big demand for IPv6 being public networks. So it will mainly be "regular client PCs" who need IPv6, and most of those already have IPv6 stacks. You might have to replace your $50 SOHO router with another $50 SOHO router. Inside the network, for things like printers, phone systems, cameras, security systems, industrial equipment, etc., you can run an IPv4 private address space. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
