Portal Home > Knowledgebase > Articles Database > Slow DNS resolve
Slow DNS resolve
Posted by d0ctor, 08-19-2011, 06:46 PM |
I just got a dedicated from WholesaleInternet and it's working great, except apt-get and wget and any other internal DNS stuff is slow as hell. I haven't set my PTR record yet with them, could that possibly be the problem?
/etc/resolv.conf
nameserver 192.168.1.100
nameserver 69.30.192.15
nameserver 69.30.192.14
/etc/hosts
127.0.0.1 localhost
..other ipv6 stuff..
PING google.com (74.125.225.50) 56(84) bytes of data.
64 bytes from 74.125.225.50: icmp_seq=1 ttl=56 time=11.8 ms
64 bytes from 74.125.225.50: icmp_seq=2 ttl=56 time=11.2 ms
^C64 bytes from 74.125.225.50: icmp_seq=3 ttl=56 time=11.2 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 10071ms
rtt min/avg/max/mdev = 11.223/11.418/11.800/0.283 ms
ifconfig
eth0 Link encap:Ethernet HWaddr 00:24:1d:c2:7c:b4
inet addr:external ip Bcastome other IP Mask:255.255.255.248
inet6 addr: fe80::224:1dff:fec2:7cb4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4716 errors:0 dropped:0 overruns:0 frame:0
TX packets:1961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:544488 (531.7 KiB) TX bytes:239028 (233.4 KiB)
Interrupt:250 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
|
Posted by Hoopla-Brad, 08-20-2011, 06:43 AM |
Lack of PTR isn't going to slow you down, what/where is 192.168.1.100?
|
Posted by eth00, 08-20-2011, 07:28 AM |
Just how slow is slow? Try doing
time dig google.com +short
That will show you how long it takes to do the resolution.
|
Posted by brianoz, 08-20-2011, 08:56 AM |
You probably aren't running a resolver on 192.168.1.100 - try commenting that line out of /etc/resolv.conf and see if the command "host google.com" is then faster.
|
Add to Favourites Print this Article
Also Read