Telnet very slow ( 3 to 4 minutes )

[Steven Schweda]

> Did you do a Forum search for keywords like,
> say,
> slow telnet
> ?

If you had, then you might know that the
usual DNS problem is not "to resolve
hostnames", it's a failure to do the
_reverse_ look-up, that is, to get the host
name from its IP address.

The Telnet _server_ tries to get the name
associated with the IP address of an incoming
connection, so it tries to do a reverse
(address-to-name) look-up of the client.
This is usually what is slow.

> 9.Tried with IP instead of Hostname still
> same

And it's why no one cares what you do on the
Telnet client system. The server needs to be
able to do that reverse look-up of the
client's address.

[s.kalaivanan]

Hi All already Saw telnet Forums ,

But This problem little confused ,

today , i have kept /etc/resolv.conf file as it is ( means orginal ) , and only changed /etc/nsswitch.conf file as { hosts: files },

Now also telnet working Normal means without renaming /etc/resolv.conf file ,my question now is this DNS issue or some other ? now lookup only from /etc/hosts okay ...

IF DNS issue what could be the problem ? already other SUN servers are working fine with same setup ,

DNS folks not accepting they are telling other servers are working fine , now what answer to tell them ,where we can focus now ?

Thanks & regards,
Kalai.

[Tingli]

It is hard to understand what you are talking about.

[Steven Schweda]

> IF DNS issue what could be the problem ?

> The Telnet _server_ tries to get the name
> associated with the IP address of an incoming
> connection, so it tries to do a reverse
> (address-to-name) look-up of the client.
> This is usually what is slow.

On the Telnet server (HP-UX) system:

nslookup ip_address_of_Telnet_client

If that works well, then I'd expect the
Telnet server to work well. If it's slow (or
fails), then I'd expect the Telnet server to
be slow to connect.

> already other SUN servers are working fine
> with same setup ,

Perhaps the Sun (Solaris?) Telnet server
doesn't care what the client's name is. The
HP-UX Telnet server seems to care.

> DNS folks not accepting they are telling
> other servers are working fine , now what
> answer to tell them [...]?

If that "nslookup" command behaves badly,
then I'd show then the evidence. (If it
works well, then I'd start looking for some
other problem.)

[Steven Schweda]

> If that "nslookup" command behaves badly,
> then I'd show then the evidence. [...]

If that "nslookup" command behaves badly,
then I'd show them the evidence. [...]

"then", "them", ... Sigh.

[s.kalaivanan]

Hi Steven Schweda,

I'm not getting your point ,

again Explain to you

1. If /etc/nsswitch.conf file as {hosts: files dns nis } --> in this conditiion nslookup / Telnet very slow

2. If I after edited /etc/nsswitch.conf file as { hosts: files } ---> In this conditon telnet working fine, means its not using resolution it using /etc/hosts . Telnet / nslookup getting normal bcoz it uses /etc/hosts so whatever entry in /etc/hosts happening normal nslookup

Thanks & Regards,
Kalai.

[Steven Schweda]

> I'm not getting your point ,

Apparently. Do this:

> On the Telnet server (HP-UX) system:
>
> nslookup ip_address_of_Telnet_client

What happens?

[s.kalaivanan]

Hi Steven Schweda ,

#nslookup --> First time slow ( means same issue like as telnet login )

Pls see my previous question

thanks & Regards,
Kalai.

[Steven Schweda]

> Pls see my previous question

Please see my previous answer.

> DNS folks not accepting they are telling
> other servers are working fine , now what
> answer to tell them ,where we can focus
> now ?

> #nslookup --> First time slow
> ( means same issue like as telnet login )

Ok, you've told me. Now, tell your "DNS
folks". (Then ask them to fix it?)


As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions and interpretations.

[s.kalaivanan]

Thanks Steven Schweda ,

I have already Escalated this to DNS team ,

I will let you know ,

Thanks & Regards,
Kalai.