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

Re: nslookup from behing router/modem



On Thu, Aug 16, 2007 at 04:15:45PM +0100, michael wrote:
> On Thu, 2007-08-16 at 15:40 +0100, michael wrote: 
> > On Thu, 2007-08-16 at 15:08 +0100, Liam O'Toole wrote:
> > > On Thu, 16 Aug 2007 13:47:30 +0100
> > > michael <cs@networkingnewsletter.org.uk> wrote:
> > > 
> > > > I have just replaced my USB modem with a router/modem and things seem
> > > > to be working find on my Debian box behind the router, except for
> > > > nslookup. Is there something I need to amend to get it to work. Note
> > > > I can still access the e-World from my Debian box:
> > > > ...
> > > > 
> > > > michael@manchester-campaigns:~$ less /etc/resolv.conf
> > > > search
> > > > nameserver 158.152.1.58
> > > > nameserver 158.152.1.42
> > > 
> > > The empty 'search' list looks wrong. Try removing the line altogether.
> > 
> > Yes, if I delete that line then it works fine. Upon rebooting I see
> > that /etc/resolv.conf which is a sym link to /etc/ppp/resolv.conf gets
> > updated:
> > ...
> ...
> 
> but somehow /etc/ppp/resolv.conf is being created at boot time with
> correct nameservers but an empty search string...
> 
> any ideas? something to do with /etc/ppp/ip*d/0000usepeerdns
> but I've no idea how/when they are used and why?!?

Probably best to browse the various manpages and such, but another approach
is to just look around for clues to the settings, e.g.,

  $ sudo find /etc/ppp -type f -exec grep -H search {} \;
  /etc/ppp/ip-up.d/0dns-up:# 'search' or 'domain' directives or additional nameservers.  Read the 

That file (on my system) may have some leads to follow:

  $ sudo less /etc/ppp/ip-up.d/0dns-up
  ...
  # 0dns-up sets up /etc/resolv.conf for the provider being connected to.  In
  # conjunction with pppd's usepeerdns option it also handles dynamic dns.
  # It expects to be passed the provider name in PPP_IPPARAM.
  
  # Pppconfig creates a file in /etc/ppp/resolv for each provider for which the
  # administrator chooses 'Static' or 'Dynamic' in the 'Configure Nameservers'
  # screen.  The files for providers for which 'Static' was chosen contain the
  # nameservers given by the administrator.  Those for which 'Dynamic' was chosen
  # are empty.  0dns-up fills in the nameservers when pppd gets them from the
  # provider when the connection comes up.  You can edit these files, adding 
  # 'search' or 'domain' directives or additional nameservers.  Read the 
  # resolv.conf manual first, though. 
  ...

Anyway, maybe such an approach could turn up an empty 'search' entry in some
file on your system... 

Good luck!

Ken

-- 
Ken Irving, fnkci+debianuser@uaf.edu



Reply to: