Openmoko Bug #2056: /etc/resolv.conf is empty on first boot
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Oct 6 14:22:56 CEST 2008
#2056: /etc/resolv.conf is empty on first boot
--------------------------------+-------------------------------------------
Reporter: rwhitby | Owner: raster
Type: defect | Status: new
Priority: normal | Milestone:
Component: Network Manager | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------------+-------------------------------------------
Comment(by newkirk):
A simple fix, provided resolvconf is installed and managing
/etc/resolv.conf, (This appears to be the case with 2007/2008/ASU/FDOM,
but not Raster's image, uncertain about others) is to add this line to
/etc/network/interfaces in the 'usb0' stanza:
up echo 'nameserver a.b.c.d' | resolvconf -a usb0
Clearly the actual destination nameserver's IP is a separate point for
potential debate, but the previous standard was the IP of the desktop to
which usb0 leads, 192.168.0.200 by current default. Another reasonable
choice would be opendns.org or another free publicly-accessible caching
DNS service.
Also best to put 'usb*' near the end of /etc/resolvconf/interface-order
just above '*' complete wildcard entry, though it will be caught by that
wildcard if not explicitly listed.
Also clearly, if one network interface's "standard" config utilizes
resolvconf to manage nameservers, ALL need to do so or problems ensue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list