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

RE: weird telnet/dns behaviour on woody



Depending on your settings, the resolver
will "try" to resolve a hostname without
a domain part by affixing some domain(s).

If (some of) the domains are external this
will cause the link to go up for the dns
query.

YMMV.

See man resolv.conf for more info.

Christian 

> -----Original Message-----
> From: Michael Pacey [mailto:mpacey@wd21.co.uk]
> Sent: Monday, September 25, 2000 1:59 AM
> To: debian-user@lists.debian.org
> Subject: weird telnet/dns behaviour on woody
> 
> 
> Hi folks
> 
> I have a couple of intel woody machines here, one originally a storm box
> and one originally a potato. I can't recall exactly when this started -
> I apt-get dist-upgrade regularly - but both are now exhibiting the
> following weird behaviour.
> 
> I run a dns server for my local network and for caching external
> lookups. I run diald with ip masquerading. When I attempt to telnet from
> either of these two boxes to any other on my network, and I enter a
> non-fully-qualified domain name, diald brings up the line before the
> telnet succeeds. If I enter the fully qualified domain name, the telnet
> works immediately.
> 
> I can ping/nslookup with or without the fqdn.... I thought this might be
> a reverse lookup problem as is often the case, but the entries on the
> dns server are right and I can nslookup the reverse entries no problem,
> i.e. nslookup 192.168.0.13 gives kermit and nslookup kermit gives
> 192.168.0.13.
> 
> I am confused; does anyone have any ideas?
> 
> TIA
> 
> --
> Michael Pacey
> michael@wd21.co.uk
> 
> wd21 ltd - world domination in the 21st century
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe 
> debian-user-request@lists.debian.org < /dev/null
> 
> 



Reply to: