Package: resolvconf Version: 1.37 Severity: normal Tags: patch If a machine has a local recursor, it makes sense to have 127.0.0.1 as the very first nameserver listed in resolv.conf.
resolvconf's libc upgrade script uses a function uniquify_nameserver_list(), which says: # Returns NSMSRVS -- space-separate list of no more than 3 items, # without duplicates, truncated after 127.* while interface-order(5) says # /etc/resolvconf/interface-order # Use nameservers on the loopback interface first. lo* [...] These two disagree and in fact, if lo and eth0 both define dns-nameservers in /e/n/i, then the libc upgrade script will *only* put the 127.0.0.1 entry into resolv.conf because it truncates the uniquified nameserver list after encounter of 127.*. I simply deleted the check for 127.* in the uniquify_nameserver_list function and it works fine. Why do you crop after 127.*? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages resolvconf depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip resolvconf recommends no packages. -- debconf information excluded -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
