Package: resolvconf Version: 1.33 Severity: important *** Please type your report below this line *** If I populate /etc/resolvconf/resolv.conf.d/base with:
nameserver 127.0.0.1 nameserver 192.168.0.1 then run resolvconf -u, my /etc/resolv.conf looks like: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search domain_not_set.invalid What happened to 192.168.0.1?? If I reverse the order of the nameservers, then I get both 192 and 127, but 127 comes last. I'm using pdnsd and want to first check my local 127.0.0.1 cache, then go on to 192 if the name is not in my local cache. resolv.conf appears to get populated correctly as long as 127.0.0.1 is not the first nameserver to be populated. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4.1027 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages resolvconf depends on: ii coreutils 5.2.1-2 The GNU core utilities ii debconf [debconf-2.0] 1.4.52 Debian configuration management sy ii initscripts 2.86.ds1-1 Standard scripts needed for bootin resolvconf recommends no packages. -- debconf information: resolvconf/bad-pppoeconf-hook: * resolvconf/downup-interfaces: * resolvconf/link-tail-to-original: false resolvconf/bad-pppconfig-hook: * resolvconf/linkify-resolvconf: true * resolvconf/disable-bad-hooks: true resolvconf/bad-xisp-hook: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
