On 06/25/10 13:12, Andrej Podzimek wrote:
Hello,
When I run OpenSolaris with IPv6 enabled, *some* (but not all) domains
are resolved incorrectly. The IPv6 address of my router is prepended
before other addresses. Programs (such as Firefox) then try to contact
my router instead of the correct server.
The problem has been revealed simply by using 'ping -a'. To
illustrate this:
$ ping -a www.sun.com
www.sun.com (2002:****:****:1::1) is alive # my router's
address (!)
www.sun.com (137.254.16.57) is alive # the correct address
$ ping -a www.zive.cz
www.zive.cz (2002:****:****:1::1) is alive # my router's
address (!)
www.zive.cz (77.93.192.144) is alive # the correct address
$ ping -a www.google.com # IPv4 Google works OK
www.google.com (74.125.87.103) is alive
www.google.com (74.125.87.104) is alive
www.google.com (74.125.87.105) is alive
www.google.com (74.125.87.106) is alive
www.google.com (74.125.87.147) is alive
www.google.com (74.125.87.99) is alive
$ ping -a ipv6.google.com # IPv6 Google works OK
ipv6.google.com (2a00:1450:8007::63) is alive
ipv6.google.com (2a00:1450:8007::67) is alive
ipv6.google.com (2a00:1450:8007::68) is alive
ipv6.google.com (2a00:1450:8007::69) is alive
ipv6.google.com (2a00:1450:8007::6a) is alive
ipv6.google.com (2a00:1450:8007::93) is alive
IPv6 works; ipv6.google.com works as well. Some domains resolve
correctly (router's address is not prepended), but some don't.
Presumably, disabling IPv6 fixes the problem. But that's not a good
solution...
Other notes:
* dig always resolves correctly, no router's address prepended.
Could you share your dig command and output please.
* Linux and FreeBSD work fine with IPv6 on the same connection.
Do they use the same nameserver in /etc/resolv.conf?
* The same issue is in 2009.06, snv_134 and snv_143.
This is /etc/inet/hosts:
::1 helium localhost loghost
127.0.0.1 helium localhost loghost
These are the two important lines from /etc/nsswitch.conf:
hosts: files dns
ipnodes: files dns
What could be the cause of this? Any ideas?
Capture what's happening on the network as you make the requests using
snoop or wireshark.
Andrej
_______________________________________________
networking-discuss mailing list
[email protected]
--
--Stacey
_______________________________________________
networking-discuss mailing list
[email protected]