https://bugzilla.novell.com/show_bug.cgi?id=684534 https://bugzilla.novell.com/show_bug.cgi?id=684534#c9 --- Comment #9 from Ralf Haferkamp <rhafer@novell.com> 2011-07-20 14:21:28 CEST --- (In reply to comment #8)
Well, we can't have it both ways. Either we do return ipv6 addresses when there's no interface with ipv6, or we don't. bug 706719 is about a system where there's no ipv6 interface, but still expects a ipv6 address to be returned. It doesn't expect an IPv6 to be returned. It only expects not to get the same IPv4 address returned twice. And at least according to the "ip" output there is an IPv6 address configured for lo (though I might just have missunderstood you):
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 52:54:00:ba:a7:83 brd ff:ff:ff:ff:ff:ff
I would be inclined to say that this expectation is wrong, and indeed the past years changes in the resolver always worked towards not returning ipv6 addresses for machines were it's reasonable sure that it doesn't have ipv6. That would be ok, but why is it returning 127.0.0.1 twice, now?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.