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

Ole Christensen ole.christensen at post.uni2.dk
Tue Mar 7 22:24:33 UTC 2000


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?

Regards,

Ole

"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 192.18.97.195: icmp_seq=0. time=130. ms
> 64 bytes from 192.18.97.195: icmp_seq=1. time=4095. ms
> 64 bytes from 192.18.97.195: icmp_seq=2. time=3095. ms
> 64 bytes from 192.18.97.195: icmp_seq=3. time=2095. ms
> 64 bytes from 192.18.97.195: icmp_seq=4. time=1096. ms
> 64 bytes from 192.18.97.195: icmp_seq=5. time=96. ms
> 64 bytes from 192.18.97.195: icmp_seq=6. time=123. ms
> 64 bytes from 192.18.97.195: icmp_seq=7. time=153. ms
> 64 bytes from 192.18.97.195: icmp_seq=8. time=160. ms
> 64 bytes from 192.18.97.195: icmp_seq=9. time=138. ms
>
> Javed
>
> _________________________________________
> Never Doubt  the Path You've Chosen




More information about the bind-users mailing list