I n i t i a l c o n n e c t i o n
matthewt at fairplay.co.uk
Wed Mar 8 09:19:33 UTC 2000
Sorry if I'm missing something here but what does DNS have to do with this?
If you used ping www.name.here it's obvious that a DNS lookup has been
successfully performed since you're getting the IP address and the DNS
lookup goes before any packets are sent. If you used ping 188.8.131.52 then
DNS was not involved since, as set up normally, ping does not do any reverse
If you are experiencing problems with Traceroute then look at the numbers -
not at the real world time it takes for the name or number to appear.
Traceroute uses DNS initially to get the IP address and then only performs a
reverse lookup AFTER it has received that hop's IP address.
What would appear to be at fault is a link or routing somewhere along the
line between you and this server.
Check with you ISP to see if they see similar.
M at t :O)
> -----Original Message-----
> From: Javed E. Malik [mailto:Javed.Malik at emis-intl.com]
> Sent: 07 March 2000 20:49
> To: DNS Mailing List
> Subject: I n i t i a l c o n n e c t i o n
> 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
> I stopped and started inetsvc. Any idea? I would appreciate your help.
> 64 bytes from 184.108.40.206: icmp_seq=0. time=130. ms
> 64 bytes from 220.127.116.11: icmp_seq=1. time=4095. ms
> 64 bytes from 18.104.22.168: icmp_seq=2. time=3095. ms
> 64 bytes from 22.214.171.124: icmp_seq=3. time=2095. ms
> 64 bytes from 126.96.36.199: icmp_seq=4. time=1096. ms
> 64 bytes from 188.8.131.52: icmp_seq=5. time=96. ms
> 64 bytes from 184.108.40.206: icmp_seq=6. time=123. ms
> 64 bytes from 220.127.116.11: icmp_seq=7. time=153. ms
> 64 bytes from 18.104.22.168: icmp_seq=8. time=160. ms
> 64 bytes from 22.214.171.124: icmp_seq=9. time=138. ms
> Never Doubt the Path You've Chosen
More information about the bind-users