[Resolvconf-devel] Bug#676183: /etc/resolv.conf is setup too late

Harald Dunkel harald.dunkel at aixigo.de
Tue Jun 5 09:12:07 UTC 2012

Package: resolvconf
Version: 1.65

It seems that /etc/resolv.conf is not setup at first time
network configuration.

See attachment. After setting up the network interfaces
some triggers tried to setup rpcbind and NFS as configured
in /etc/fstab, but the NFS server host names could not be
resolved. /etc/resolv.conf was still empty (except for the
default comment) when I got a login.

After a manual

	ifdown br0
	ifup br0

/etc/resolv.conf is setup correctly, and

	mount -a

mounts the missing NFS filesystems. But of course I would
prefer if this happens automagically at boot time.

/etc/network/interfaces is

	auto lo
	iface lo inet loopback

	auto br0
	iface br0 inet static
		bridge_ports eth0
		bridge_fd 9
		bridge_hello 2
		bridge_maxage 12
		bridge_stp off
		# dns-* options are implemented by the resolvconf package, if installed
		dns-search ac.mydomain.de. vs.mydomain.de mydomain.de.

For Squeeze there is no such problem.

Any helpful comment would be highly appreciated. Please reassign
this bug report, if necessary.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: IMG_0769.PNG
Type: image/png
Size: 865419 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20120605/5b7c4db0/attachment-0001.png>

More information about the Resolvconf-devel mailing list