I n i t i a l C o n n e c t i o n

Javed E. Malik jemalik at emis-intl.com
Tue Mar 7 23:01:33 UTC 2000

Hi Ole,

Yes I tested with traceroute command. The problem is that it takes time in
the beginning to make connection. Once the connection is open it does not
take long time to go to next hop. Any other hint to check the DNS response



::-----Original Message-----
::From: Ole Christensen [mailto:ole.christensen at post.uni2.dk]
::Sent: Tuesday, March 07, 2000 5:25 PM
::To: Javed E. Malik
::Cc: DNS Mailing List
::Subject: Re: I n i t i a l C o n n e c t i o n
::DNS is not involved at this stage (only once before sending out
::any packets if
::you do a "ping hostname", when resolving hostname to IP-address). So your
::problem must be found otherwhere. Have you tried traceroute?
::"Javed E. Malik" wrote:
::> Hi all,
::> Following is the output from the ping command. It looks like DNS takes
::> longer time to translate the address or some other reason. Both
::NIS and DNS
::> are working on our system. I have set hosts: dns files in nsswitch.conf
::> file.
::> I stopped and started inetsvc. Any idea? I would appreciate your help.
::> 64 bytes from icmp_seq=0. time=130. ms
::> 64 bytes from icmp_seq=1. time=4095. ms
::> 64 bytes from icmp_seq=2. time=3095. ms
::> 64 bytes from icmp_seq=3. time=2095. ms
::> 64 bytes from icmp_seq=4. time=1096. ms
::> 64 bytes from icmp_seq=5. time=96. ms
::> 64 bytes from icmp_seq=6. time=123. ms
::> 64 bytes from icmp_seq=7. time=153. ms
::> 64 bytes from icmp_seq=8. time=160. ms
::> 64 bytes from icmp_seq=9. time=138. ms
::> Javed
::> _________________________________________
::> Never Doubt  the Path You've Chosen

More information about the bind-users mailing list