[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#299554: In dialup install, nameserver addresses are not written to resolv.conf

On Wed, 2005-03-30 at 13:38 -0400, Tony Rowe wrote:
> On Mon, Mar 14, 2005 at 07:19:36PM -0400, Tony Rowe wrote:
> > Now here's the rub.  During the base-config stage and if one's dialup ISP 
> > has assigned nameservers, one therefore selects "static DNS" from the 
> > appropriate menu in pppconfig, filling in dotted quads for primary and 
> > secondary nameservers.  pppconfig writes this information to 
> > /etc/ppp/resolv/provider *only*, and does not seem to write 
> > /etc/resolv.conf at all.

The nameserver entries should be written to /etc/resolv.conf when the
PPP interface is brought up.  /etc/ppp/ip-up.d/0dns-up does this.

> > Therefore configure apt barfs and base-config 
> > leaves the install broken (un-updateable) until something like
> > 
> > # cp /etc/ppp/resolv/provider /etc/resolv.conf
> > 
> > is done manually.

I don't understand.  pppconfig is run and /etc/ppp/resolv/provider is
written; then the ppp interface is brought up; but /etc/resolv.conf is
not written?

> Some additional information.  It seems that dynamic DNS can be used with
> my ISP after all <sigh>; that the correct nameserver addresses will be
> negotiated successfully and a /etc/resolv.conf created properly (using
> usepeerdns) as the connection is being brought up, but only if dynamic
> DNS (rather than static DNS) is selected during the pppconfig session. 

So /etc/ppp/ip-up.d/0000usepeerdns does succeed in
writing /etc/resolv.conf.

> Indeed
> static DNS does work and the addresses in /etc/ppp/resolv/provider are
> used to generate an /etc/resolv.conf as the connection is brought up if
> an /sbin/resolvconf exists.

So this line in 0dns-up works too:

    /sbin/resolvconf -a "${PPP_IFACE}.pppconfig" < "$PPPRESOLV/$PROVIDER"

> However resolvconf is not included on the
> netinst iso as far as I can tell.

Right.  It is not included.  (Maybe in etch.)

> So, if static DNS is selected in pppconfig and resolvconf exists,
> resolvconf does something desirable that in its absence the script
> /etc/ppp/ip-up.d/0dns-up fails to do, at least in this case.  Any
> pointers or suggestions are welcome.

Can you trace 0dns-up to see what goes wrong?  E.g., does

    grep " / " /proc/mounts | grep -q " rw "

produce a nonzero status resulting in "exit 0"?  Can you add

    set -x

to the top of the script and view the result?

> Finally, this part of my bug if
> not due to some folly of my own, seems to reside with pppconfig and not
> with the debian-installer netinst iso as such.

Perhaps, but let's try to find the bug before reassigning the report.

P.S. Are you on Cape Breton?
Thomas Hood <jdthood@aglu.demon.nl>

Reply to: