[Bug 988084] [NEW] Precise: Static IP Results in Empty /etc/resolv.conf

[Ross Peoples]

Public bug reported:

I have seen reports of this during upgrades from 11.10 to 12.04, but I
am seeing this with a fresh install of Ubuntu 12.04.

Steps to reproduce:

1) Install a new 12.04 server installation
2) Edit /etc/network/interfaces and set:
    iface eth0 inet dhcp to static, and enter address, netmask, gateway, network, broadcast
3) Reboot
4) cat /etc/resolve.conf results in an empty file, aside from the warning about the file being auto-generated

There are only two workarounds for this that I've found:
1) Edit /etc/resolvconf/resolv.conf.d/head and add the desired settings to the bottom of the file.
- OR -
2) Disable the resolvconf daemon from startup and setup /etc/resolv.conf as usual.

Sorry if this is already a known issue from a FRESH install, but I was
only able to find references to this problem in relation to upgrades.

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/988084

Title:
  Precise: Static IP Results in Empty /etc/resolv.conf

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  I have seen reports of this during upgrades from 11.10 to 12.04, but I
  am seeing this with a fresh install of Ubuntu 12.04.

  Steps to reproduce:

  1) Install a new 12.04 server installation
  2) Edit /etc/network/interfaces and set:
      iface eth0 inet dhcp to static, and enter address, netmask, gateway, network, broadcast
  3) Reboot
  4) cat /etc/resolve.conf results in an empty file, aside from the warning about the file being auto-generated

  There are only two workarounds for this that I've found:
  1) Edit /etc/resolvconf/resolv.conf.d/head and add the desired settings to the bottom of the file.
  - OR -
  2) Disable the resolvconf daemon from startup and setup /etc/resolv.conf as usual.

  Sorry if this is already a known issue from a FRESH install, but I was
  only able to find references to this problem in relation to upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/988084/+subscriptions