RE: [MLUG] DNS question

[yoda <EMAIL:PROTECTED>]

Hm.... something of which I hadn't thought: Is there a way to tell all
hosts on a network to do this (Win/Linux mixed environment). We use DHCP,
but I can't seem to find anything in either man page or on the web.

Well, actually, I found how to make BIND do it, but I'm using DJB's
dnscache, and it seems like something the client should be doing anyway,
not the server.

On Mon, 11 Feb 2002, yoda wrote:

> Very much appreciated. That explains it.
> 
> On Mon, 11 Feb 2002, Rick Buford wrote:
> 
> > resolver options (from man resolv.conf):
> >  ndots:n   sets a threshold for the number of dots which must
> >                         appear in a name given to res_query() (see
> >                         resolver(3)) before an initial absolute query will
> > be
> >                         made.  The default for n is ``1'', meaning that if
> >                         there are any dots in a name, the name will be tried
> >                         first as an absolute name before any search list
> > ele­
> >                         ments are appended to it.
> > 
> > see also "man nsswitch.conf"
> > 
> > Rick 
> > "I'm not sure which upsets me more: that people are so unwilling
> > to accept responsibility for their own actions, or that they are
> > so eager to regulate everyone else's." -- Kee Hinckley
> > 
> > >-----Original Message-----
> > >From: yoda [mailto:EMAIL:PROTECTED]
> > >Sent: Monday, February 11, 2002 1:37 PM
> > >To: EMAIL:PROTECTED
> > >Subject: [MLUG] DNS question
> > >
> > >
> > >Hullo. I was wondering about how the search line in /etc/resolv.conf
> > >works. I was under the impression it searched what was in there first,
> > >before trying just the exact name.
> > >
> > >For example:
> > >if resolv.conf reads:
> > >search foo.bar
> > >nameserver 127.0.0.1
> > >
> > >and I tried:
> > >ping www.kernel.org
> > >
> > >I was under the impression it'd try
> > >www.kernel.org.foo.bar
> > >and then
> > >www.kernel.org
> > >
> > >I wanted to change this behaviour because our (masq'ing) 
> > >firewall forwards
> > >port 80 to an internal machine, and it seems not to work when 
> > >an internal
> > >machine attempts to connect to the external ip of the firewall.
> > >
> > >I added an alias for tinydns, but when I ping, it still comes back from
> > >the external ip of the firewall.
> > >
> > >If anyone knows why or (even better) knows a better way of fixing the
> > >port forwarding+masq'ing problem, I'd appreciate the help.
> > >
> > >--
> > >To unsubscribe, go to http://mlug.missouri.edu/members/edit.php
> > >
> > >Archives are available at http://mlug.missouri.edu/list-archives/
> > >
> > --
> > To unsubscribe, go to http://mlug.missouri.edu/members/edit.php
> > 
> > Archives are available at http://mlug.missouri.edu/list-archives/
> > 
> 
> --
> To unsubscribe, go to http://mlug.missouri.edu/members/edit.php
> 
> Archives are available at http://mlug.missouri.edu/list-archives/
> 

--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/