IPv6 DNS - Can't visit webpage

[Borvik]

I've posted this in the "DNS/BIND/DHCP/WINS Issues" forum - but this may be more specific to Vista, so I've decided to post here as well.

This problem is really strange.

It all stemmed from the fact that we couldn't access a website.

I have since run the nslookup command on numerous PCs. My two PCs seem to be the only two that are reporting multiple IP addresses (looks like a botched AAAA - IPv6 - query). The rest of the machines all report the single correct IPv4 address.

This is where it gets confusing - all the XP machines work fine, while all the Vista machines fail. The Vista machines fail even though nslookup reports only the one correct IP address!

I do know it has something to do with the IPv6 lookups, as I disabled that in Firefox's about:config page - and I was then able to load the page (only in Firefox though).

Any ideas on what I can do to fix the problem?

 

[smah]

Have they been updated to SP1? There were a few fixes related to IPv6

 

[Borvik]

I don't know about ALL the Vista machines, but two of the ones I did test this on HAVE been updated to SP1.

 

[linney]

Anything interesting here?

Check your IPv6 configuration

http://www.ipv6day.org/action.php?n=En.Configuration-WindowsVista

Long page and image load

http://www.soldatforums.com/index.p...775ffba5&topic=29666.from1220534004;topicseen

 

[Borvik]

The IPv6 returned from the nslookup doesn't look (debug mode) doesn't appear to be a valid IPv6 address, and it is then being misinterpreted as an IPv4 address.

AAAA record result - ::ffff:###.##.###.###

The nslookup result then lists just the # sign part of that result as the result.

Could it be possible that the DNS server that hosts the address in question is incorrectly configured for IPv6?

 

[pudda]

Uncheck the IPv6 in the network properties and try it again- some DNS servers do not use IPv6. Ran across this with a few XP machines that somehow got IPv6 on them and had the same results, so deleted the IPv6 (can only uncheck in Vista without reg editing) and was back to surfing.

The test continues...