On Fri, Feb 4, 2011 at 3:11 PM, Phil Brutsche <[email protected]> wrote: > Why would it not work? Any reasonable operating system that only has > IPv4 connectivity will recognize that it won't be able to connect to > IPv6 content and won't even try. You will only have a problem when the > content is IPv6-only.
Your last sentence is my entire point. Look at step #2 below. >>> 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. -- 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
