[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9951.0. "Slow telnet via DNS" by NNTPD::"[email protected]" (Adrian Morrisson) Tue May 27 1997 06:08

Hi.
	I have a customer who has just set up a few DU4.0b machines. They have
configured the machines as DNS clients. When an attempt to login to the
machine is done from any device where it's IP address is not able to be
resolved
from either the hosts file or by performing a DNS lookup the login prompt will

not appear for approximately 20 seconds. Is there a way of improving this?
This isn't happening with their 3.2x machines. The /etc/svc.conf has 
hosts=local,bind and I can't see any obvious differences between the 3.2 and
4.0
machines.

Any suggestions etc will be welcome.

Thanks

Adrian Morrisson




[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
9951.1SMURF::MAJESKETue May 27 1997 12:303
    Can you give more detail about the setup?
    
    Is the customer using NIS to distribute user/group information?
9951.2BIGUN::nessus.cao.dec.com::MayneMeanwhile, back on Earth...Tue May 27 1997 19:088
DNS is probably set up incorrectly such that the reverse lookups on that machine 
aren't being resolved correctly. Try doing an nslookup on one of the IP 
addresses and see what happens.

If this is the problem, fix reverse DNS lookups. (Didn't something change 
between 3.2x and 4.0 in this area?)

PJDM
9951.3More infoNNTPD::"[email protected]"Adrian MorrissonWed May 28 1997 03:1424
Hi
	I wouldn't have thought NIS would be involved as the customer is 
telneting from no unix machines.
 
The problem occurs when the client machine has an IP address which is not 
in the same subnet as the server and the client IP address can not be 
resolved by performing a reverse look up on the domain name server (that 
is, resloving the client name from the IP address).
It makes no difference what the client is, the result is the same whether 
it is a router, a pc (NT, W3.1, etc), or another unix based system.
The clients experience the problem when both the IP address and a fully 
qualified DNS name is used.

Nslookup client results in "can't find client: non-existent host/domain".
This is to be expected as the root of the problem is that the delay when the 
client machine is not in the dns database.

Nslookup server from a unix machine with domain name services enabled 
resolves the name without a problem.

Thanks

Adrian Morrisson
[Posted by WWW Notes gateway]
9951.4BIGUN::nessus.cao.dec.com::MayneMeanwhile, back on Earth...Wed May 28 1997 03:183
So is the problem fixed or not?

PJDM
9951.5Still happeningNNTPD::"[email protected]"Adrian MorrissonWed May 28 1997 03:526
The problem is still occuring.

Thanks

Adrian
[Posted by WWW Notes gateway]