| View previous topic :: View next topic |
| Author |
Message |
dE_logics
Advocate
Joined: 02 Jan 2009
Posts: 2290
Location: $TERM
|
 Posted: Sat Mar 12, 2011 8:03 am Post subject: name resolution too slow. |
 |
|
I've installed and running djbdns's tinydns for name resolution, however it appears the resolution is very slow.
When I ping using a DNS name, the name resolution line (PING www.xyz.net (192.168.1.1) 56(84) bytes of data) pops up at that moment, but the actual ping response come up very late.
For e.g. a single ICMP ping takes 5 seconds. There're no packet losses however.
_________________
My blog |
|
| Back to top |
|
 |
gentoo_dude
l33t
Joined: 08 May 2004
Posts: 645
Location: Washington, DC
|
| Posted: Sat Mar 12, 2011 6:35 pm Post subject: |
|
|
| Quote: | | When I ping using a DNS name, the name resolution line (PING www.xyz.net (192.168.1.1) 56(84) bytes of data) pops up at that moment, but the actual ping response come up very late. |
The name resolution is actually fast: since the computer already knows the IP address for www.xyz.net. What is slow is for ICMP package to reach the destination and come back with a response. But this is not resolution of name, but routing. So that is where the problem lies. If the name resolution was slow, then it will take seconds for the message to show. |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Sat Mar 12, 2011 7:18 pm Post subject: |
|
|
| Check it in wireshark to see where the delay comes from. You can set it to show timestamps as the difference from the last packet. |
|
| Back to top |
|
|
dE_logics
Advocate
Joined: 02 Jan 2009
Posts: 2290
Location: $TERM
|
| Posted: Sun Mar 13, 2011 12:55 pm Post subject: |
|
|
I'll try wireshark... thanks.
_________________
My blog |
|
| Back to top |
|
|
|
Networking & Security
