Package: resolvconf Version: 1.43 Severity: important Hi.
I'm not sure if this is actually resolvconf's fault but at least it seems to be somehow connected. The resolvconf hooks are in /etc/network/if-up.d/000resolvconf and I'd assume from this, that /etc/resolv.conf should be set up already, when if-post-up-stuff ist executed (and these scripts should already have DNS available. But it seems that it's not the case. I stumbled across this when doing the following: I wanted to set up iptables rules via pre-up/post-up/etc in /etc/network/interfaces (using iptables-restore). Now I think one should be able to assume, that in post-up, DNS is already available. I have a special set of iptables rules which is loaded pre-up, in order to secure the interface, even before it's brought up. And in post-up I have my actual rules (which also use some hostnames, as source-addresses or so...). But this doesn't work, as DNS is not yet available in post-up. When I move resolvconf's hooks to /etc/network/if-pre-up.d/ it works, and DNS is available. Could this be some timing issue? Any ideas? Thanks, Chris. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages resolvconf depends on: ii coreutils 6.10-6 The GNU core utilities ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip resolvconf recommends no packages. resolvconf suggests no packages. -- debconf information: resolvconf/bad-pppconfig-hook: * resolvconf/linkify-resolvconf: true * resolvconf/disable-bad-hooks: true resolvconf/bad-pppoeconf-hook: * resolvconf/downup-interfaces: * resolvconf/link-tail-to-original: false resolvconf/bad-xisp-hook:
smime.p7s
Description: S/MIME cryptographic signature
