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

Bug#182886: libc6: local hostnames containing a dot get forwarded outside when doing host-lookups.



reassign 182886 manpages
thanks

At Fri, 07 Mar 2003 18:28:17 +0900,
GOTO Masanori wrote:
> At Sun, 2 Mar 2003 19:18:02 +0100,
> Bernhard R. Link <brl@pcpool00.mathematik.uni-freiburg.de> wrote:
> > * Vassilii Khachaturov <vassilii@tarunz.org> [030228 21:58]:
> > > > Thanks, I missed that. Being placed unter "internal variables" and
> > > > "debug" seems to have tricked me in ignoring this part.
> > > > 
> > > > There should at least be a sentence "search" to indicate that one has
> > > > to read the ndots-part to get a real search-path.
> > 
> > I've tested this some people by letting them open resolv.conf and
> > describing the problem. Noone found anything until they were told
> > to look for "options ndots". I suggest adding something like the
> > following to the manpage:
> > 
> > --- resolv.conf.5.orig  Sun Mar  2 18:10:44 2003
> > +++ resolv.conf.5       Sun Mar  2 18:34:38 2003
> > @@ -72,8 +72,14 @@
> >  This may be changed by listing the desired domain search path
> >  following the \fIsearch\fP keyword with spaces or tabs separating
> >  the names.
> > -Most resolver queries will be attempted using each component
> > +Resolver queries having less than 
> > +.B ndots 
> > +dots (default is 1) in them will be attempted using each component
> >  of the search path in turn until a match is found.
> > +For environments with multiple subdomains please read 
> > +.B options ndots:n
> > +below to avoid man-in-the-middle attacks and unnecessary
> > +traffic for the root-dns-servers.
> >  Note that this process may be slow and will generate a lot of network
> >  traffic if the servers for the listed domains are not local,
> >  and that queries will time out if no server is available
> >
> > 
> > I think this should fix the problem of misleading documentation.
> 
> Fixing inappropriate description is everytime fine.  resolv.conf.5
> is in manpages package, so could I reassign this bug to manpages?

I reassign it to manpages package.

-- gotom



Reply to: