https://bugzilla.novell.com/show_bug.cgi?id=765638 https://bugzilla.novell.com/show_bug.cgi?id=765638#c2 Michael Matz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@suse.com --- Comment #2 from Michael Matz 2012-06-06 10:19:57 UTC --- Output of 'ip a', 'ip r' and 'ip -6 r' please. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=765638 https://bugzilla.novell.com/show_bug.cgi?id=765638#c4 --- Comment #4 from andreas bittner 2012-06-06 10:50:40 UTC --- just did another host microsoft.com again and it fails host microsoft.com Host microsoft.com not found: 3(NXDOMAIN) and messages is logging lots of ipv6 trouble again Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2a01:111:2020::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2a01:111:2020::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2a01:111:2020::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2a01:111:2020::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2404:f800:2003::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2a01:111:200f:1::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving './NS/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns1.msft.net/A/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns3.msft.net/A/IN': 2a01:111:2005::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns4.msft.net/A/IN': 2a01:111:2006:6::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns5.msft.net/A/IN': 2a01:111:2020::1:1#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2001:500:1::803f:235#53 Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'ns2.msft.net/A/IN': 2a01:111:2020::1:1#53 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=765638 https://bugzilla.novell.com/show_bug.cgi?id=765638#c6 --- Comment #6 from andreas bittner 2012-06-06 11:01:59 UTC --- I have been using named for many years now, its simply a resolver for the local network asking the rootservers directly, nothing fancy. what about that other bug i pointed at with the glibc issues, I wonder if that needs to be released to the opensuse product line as well? this stuff is happening more and more the more the whole network moved closer to ipv6 deployment why would the operating system and its apps try to use the ipv6 results if the whole system was using ipv4 on their network interfaces. there must be some api or layer where this gets messed up and ipv6 preferred or it seems that sometimes only the ipv6 gets used or come first and the ipv4 results in results for name lookup gets completely disregarded and not being payed attention to :(( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=765638 https://bugzilla.novell.com/show_bug.cgi?id=765638#c8 andreas bittner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|abittner@abittner.de | --- Comment #8 from andreas bittner 2012-06-06 11:31:23 UTC --- I wonder what actual standards and specs say to this whole field of problems with multiple addresses to a name lookup see also https://bugzilla.redhat.com/show_bug.cgi?id=524194 sometimes opensuse, bind/named or whatever part of the system simply seems to stick with ipv6 addresses and ultimately fail then when the system cannot do ipv6 communication. the lookup to a name (e.g. microsoft.com) still succeeds but ipv6 lookup results (strings) are offered in the reply packets via ipv4, and the next step then eventually fails or something I presume. I strongly feel that there is some glitch or bug in the selection and handling of mixed ipv4/ipv6 name lookup results, even if first ipv6 communication or is tried and then fails, it seems that at many times no consecutive ipv4 communication is being initiated and tried. everything just dies with whatever kind of failure and problem. my easiest example was the single host microsoft.com resulting in host microsoft.com Host microsoft.com not found: 3(NXDOMAIN) with the corresponding logs of named and ipv6 network unreachable errors Jun 6 12:49:03 tuxbox named[4425]: error (network unreachable) resolving 'microsoft.com/A/IN': 2a01:111:2020::1:1#53 so its either a bind error or whatever network layer there is (in the kernel?) that actually tries to connect to an ipv6 address although the whole system doesnt have ipv6 addresses in use anywhere on the network stack at all. so by thinking about this, it cant even be just a bind error, it must be some mess at multiple places. after all ipv6 hasnt just appeared from around the corner and isnt exactly brand new any more, and still we are having all these pains caused by the mixing of ipv4 and ipv6 -- 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.