Hi,
> > Actually, scratch that. The traffic we're still getting seems to be Google/Youtube. There's no AAAA now, so obviously some clients have hung onto the cached record for rather longer than they should.
>
> MacOS X caching behaviour turned out to be very interesting. I posted something about that yesterday, but it seems to be deeper than that.
>
> It's as if OS X will just ignore AAAA responses if they don't come back quickly enough, and thus you 'lock' into IPv4 if the A response arrives quickly. I need to rig up some tests, but if anyone has looked in detail at that already and has the info, it would be appreciated.
it takes the 'latest' result thats active (it appears) - so if you open a browser
and go to a site that has A and AAAA then it uses A, if you then open a terminal,
ping6 the address and then reload the page in the browser , it'll use IPv6 address instead.
there used to be ways into the browser to change its behaviour - eg make http act like
https (which seems to favour AAAA) - but recent versions seem to have lost that hack/hook (you
have to enable the internal (hidden) developer and debug menus for safari)
OSX behaviour changed from leopard -> snow leopard and its expected to change again with Lion
alan
|