/etc/network/interfaces new requirement for dns-nameservers line is not well documented

Bug #1043335 reported by Adam Funk
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

On one machine I have a static (LAN) IP address configured manually in /etc/network/interfaces, and I have not had to modify that file for several years. Immediately after upgrading to precise, the machine had no DNS, and I eventually discovered that I needed to add a dns-nameservers line to the "iface eth0 inet static" stanza. This is not documented in "man interfaces" and the fix was hard to find. I think it should be better documented, and the upgrade process should probably suggest it.

Tags: bitesize

Related branches

Revision history for this message
Adam Funk (a-funk) wrote :

According to dpkg and aptitude, my system has the resolvconf package installed, not openresolv.

affects: openresolv (Ubuntu) → resolvconf (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

It is documented in the 12.04 release notes, and the installer has been adding this line automatically for years whenever static networking is selected at install time.

It's probably reasonable to also have it documented in interfaces(5), or at least a link provided to the resolvconf manpage, although I think it's unlikely that users will look there first when trying to debug why their nameserver entries have disappeared. That manpage belongs to the ifupdown package, so reassigning.

affects: resolvconf (Ubuntu) → ifupdown (Ubuntu)
Changed in ifupdown (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Thomas Hood (jdthood) wrote :

This was requested in Debian bug #388454 and rejected by the Debian maintainer.

However, as resolvconf is now a standard part of Ubuntu there is a pretty good reason at least to mention the dns-* options, or resolvconf(8), in interfaces(5).

Steve Langasek (vorlon)
tags: added: bitesize
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ifupdown - 0.7.2ubuntu1

---------------
ifupdown (0.7.2ubuntu1) quantal; urgency=low

  * Merge ifupdown 0.7.2 from Debian. Remaining changes:
    - If the /etc/NetworkManager/NetworkManager.conf file is present
      but doesn't have the "ifupdown:managed" the previous upload instructed
      the iniparser to return -1, which evaluates to TRUE. We instead instruct
      it to return 0, as we shouldn't prevent ifupdown from managing the
      interfaces in that case, as NM won't either. (LP: #281984)
    - debian/postinst: If the loopback interface is missing from the config
      in /etc/network/interfaces, add it on upgrade.
    - Add jobs and hooks for upstart.
  * Remove /etc/default/networking as the upstart job doesn't use it and
    can't really use it without some significant changes (support exclusion
    lists in all the upstart jobs).
  * Add resolvconf (8) to SEE ALSO section of the interfaces manpage.
    (LP: #1043335)

ifupdown (0.7.2) unstable; urgency=low

  * Don't install /etc/default/networking as executable (Closes: #679623).
  * Declare Breaks on dhcp-client (<< 3.0) instead of Conflicts.
  * Implement --no-scripts option (LP: #258782).
  * Calculate the length of a string properly (Closes: #681431).
  * When bringing hotplug interfaces up, strip VLAN and alias identifiers out
    (Closes: #680042).
  * LSB headers: depend on urandom.
  * Recognize vlan+alias combination and filter aliases out (Closes: #679672).
  * Work-around ip(8) understanding of 0NNN as octal numbers (Closes: #684698).
 -- Stephane Graber <email address hidden> Thu, 13 Sep 2012 11:18:07 -0400

Changed in ifupdown (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.