The resolvconf package is installed and the network-manager package is not.
Relevant part of /etc/network/interfaces:
----
# The primary network interface
auto eth0
iface eth0 inet static
address 130.225.51.87
netmask 255.255.255.0
network 130.225.51.0
broadcast 130.225.51.255
gateway 130.225.51.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 130.225.51.16 130.225.51.19 130.225.51.99
dns-search es.aau.dk
----
After boot /etc/resolv.conf contains:
-----
# 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
-----
Doing 'ifdown eth0' followed by 'ifup eth0' will do the right thing.
Conclusion:
=========
The resolvconf package works fine if the interface is brought up via the command line, but during boot it writes a useless /etc/resolv.conf file.
The ifup command takes a long time to complete which may hint at further problems.
I can confirm the bug.
The resolvconf package is installed and the network-manager package is not.
Relevant part of /etc/network/ interfaces:
----
# The primary network interface
auto eth0
iface eth0 inet static
address 130.225.51.87
netmask 255.255.255.0
network 130.225.51.0
broadcast 130.225.51.255
gateway 130.225.51.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 130.225.51.16 130.225.51.19 130.225.51.99
dns-search es.aau.dk
----
After boot /etc/resolv.conf contains:
-----
# 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
-----
Doing 'ifdown eth0' followed by 'ifup eth0' will do the right thing.
Conclusion:
=========
The resolvconf package works fine if the interface is brought up via the command line, but during boot it writes a useless /etc/resolv.conf file.
The ifup command takes a long time to complete which may hint at further problems.