Bug#535504: libc6: resolving: does not try different nameserver anymore
On Fri, Jul 03, 2009 at 02:50:54AM +0200, Aurelien Jarno wrote: On Thu, Jul 02, 2009 at 08:15:29PM +0200, Kurt Roeckx wrote: Package: libc6 Version: 2.9-12 Hi, It seems that libc6 doesn't try the other nameserver anymore when the first returns 5(REFUSED). If a nameserver returns REFUSED, it's not the same as a permanent error. Atleast apt-get in stable and testing/unstable react different to this. Did you tried version 2.9-18 ? A big part of the resolving code has been changed between 2.9-12 and 2.9-18. 2.9-18 behaves the same. Kurt -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535504: libc6: resolving: does not try different nameserver anymore
Package: libc6 Version: 2.9-12 Hi, It seems that libc6 doesn't try the other nameserver anymore when the first returns 5(REFUSED). If a nameserver returns REFUSED, it's not the same as a permanent error. Atleast apt-get in stable and testing/unstable react different to this. Kurt -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535504: libc6: resolving: does not try different nameserver anymore
On Thu, Jul 02, 2009 at 08:15:29PM +0200, Kurt Roeckx wrote: Package: libc6 Version: 2.9-12 Hi, It seems that libc6 doesn't try the other nameserver anymore when the first returns 5(REFUSED). If a nameserver returns REFUSED, it's not the same as a permanent error. Atleast apt-get in stable and testing/unstable react different to this. Did you tried version 2.9-18 ? A big part of the resolving code has been changed between 2.9-12 and 2.9-18. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
