wondering about setting up a local DNS cache [resolved]

[mmmmna]

can you post the content of your /etc/resolv.conf ?
additionally can you check the status of the services resolvconf and nscd:
chkconfig --list resolvconf
chkconfig --list nscd

Of course I can post that!

BTW, a post ago, I dropped using Google as my DNS and returned to the OpenDNS as set in my wireless router.

Code:

[mmmmna@localhost ~]$
[mmmmna@localhost ~]$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
[mmmmna@localhost ~]$ chkconfig --list resolvconf
resolvconf      0:off   1:off   2:on    3:on    4:on    5:on    6:off   7:off
[mmmmna@localhost ~]$ chkconfig --list nscd
nscd            0:off   1:off   2:off   3:on    4:on    5:on    6:off   7:off
[mmmmna@localhost ~]$
[mmmmna@localhost ~]$

[AS]

can you post the content of your /etc/resolv.conf ?
additionally can you check the status of the services resolvconf and nscd:
chkconfig --list resolvconf
chkconfig --list nscd

Of course I can post that!

BTW, a post ago, I dropped using Google as my DNS and returned to the OpenDNS as set in my wireless router.

Code:

[mmmmna@localhost ~]$
[mmmmna@localhost ~]$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.1
[mmmmna@localhost ~]$ chkconfig --list resolvconf
resolvconf      0:off   1:off   2:on    3:on    4:on    5:on    6:off   7:off
[mmmmna@localhost ~]$ chkconfig --list nscd
nscd            0:off   1:off   2:off   3:on    4:on    5:on    6:off   7:off
[mmmmna@localhost ~]$
[mmmmna@localhost ~]$

try the following (your result should be something less than 10 ms):
ping -c 5 192.168.1.1

from PCC -> Network and Internet -> Network center -> {choose your wireless connection} -> click button advanced settings and mark disable IPv6

turn off resolvconf service:
chkconfig resolvconf off

verify using:
chkconfig --list resolvconf

reboot your system   <<-----------

then try to surf the net ...

AS

[muungwana]

so you send your DNS request to your router and then your router send them to openDNS? How sure are you that the router is not the one slowing you down?

Try setting the dns server on your computer(in /etc/resolv.conf) and see if you still experience the slowdown

did turning off ipv6 in firefox make any difference?

[muungwana]

try the following (your result should be something less than 10 ms):
ping -c 5 192.168.1.1

He can go online and hence the address is valid and his problem is with DNS response time hence this test is not very useful since it doesnt check for DNS requests response time

[AS]

try the following (your result should be something less than 10 ms):
ping -c 5 192.168.1.1

He can go online and hence the address is valid and his problem is with DNS response time hence this test is not very useful since it doesnt check for DNS requests response time

of course, wanted to be sure that the wireless connection was working as expected ... but you are right wireless is working because of previous pings results ...

[mmmmna]

try the following (your result should be something less than 10 ms):
ping -c 5 192.168.1.1

My Results:

Code:

[mmmmna@localhost ~]$ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=2.17 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=50.8 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.835 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=2.31 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4053ms
rtt min/avg/max/mdev = 0.711/11.369/50.817/19.735 ms
[mmmmna@localhost ~]$ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.910 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.678 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=1.51 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.788 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.915 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4350ms
rtt min/avg/max/mdev = 0.678/0.960/1.513/0.292 ms
[mmmmna@localhost ~]$

from PCC -> Network and Internet -> Network center -> {choose your wireless connection} -> click button advanced settings and mark disable IPv6

Ok, will do this much, but not the rest until after I get to respond to muungwana.

[Was_Just19]

$ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=2.17 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=50.8 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.835 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=2.31 ms

There is something not right with this .......  especially the one marked ....... 

[mmmmna]

so you send your DNS request to your router and then your router send them to openDNS? How sure are you that the router is not the one slowing you down?

ALL of my times were taken by going through an unchanged configuration: the wireless router (Netgear WNR2000) then on to the DSL modem (Actiontec 704c). Everyone in the house is wireless.

Try setting the dns server on your computer(in /etc/resolv.conf) and see if you still experience the slowdown

In a moment or 2.

did turning off ipv6 in firefox make any difference?

Yes, it did.

$ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=2.17 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=50.8 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.835 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=2.31 ms

There is something not right with this .......  especially the one marked ....... 

Even when you consider that there are 2 other PCs using the network at the same time? More of the same:

Code:

[mmmmna@localhost ~]$ ping -c 50 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_req=1 ttl=64 time=1.25 ms
64 bytes from 192.168.1.1: icmp_req=2 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=3 ttl=64 time=0.686 ms
64 bytes from 192.168.1.1: icmp_req=4 ttl=64 time=0.926 ms
64 bytes from 192.168.1.1: icmp_req=5 ttl=64 time=0.659 ms
64 bytes from 192.168.1.1: icmp_req=6 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=7 ttl=64 time=0.823 ms
64 bytes from 192.168.1.1: icmp_req=8 ttl=64 time=0.818 ms
64 bytes from 192.168.1.1: icmp_req=9 ttl=64 time=0.690 ms
64 bytes from 192.168.1.1: icmp_req=10 ttl=64 time=0.701 ms
64 bytes from 192.168.1.1: icmp_req=11 ttl=64 time=0.690 ms
64 bytes from 192.168.1.1: icmp_req=12 ttl=64 time=1.16 ms
64 bytes from 192.168.1.1: icmp_req=13 ttl=64 time=0.698 ms
64 bytes from 192.168.1.1: icmp_req=14 ttl=64 time=0.688 ms
64 bytes from 192.168.1.1: icmp_req=15 ttl=64 time=0.685 ms
64 bytes from 192.168.1.1: icmp_req=16 ttl=64 time=0.629 ms
64 bytes from 192.168.1.1: icmp_req=17 ttl=64 time=0.659 ms
64 bytes from 192.168.1.1: icmp_req=18 ttl=64 time=0.675 ms
64 bytes from 192.168.1.1: icmp_req=19 ttl=64 time=0.685 ms
64 bytes from 192.168.1.1: icmp_req=20 ttl=64 time=0.683 ms
64 bytes from 192.168.1.1: icmp_req=21 ttl=64 time=0.705 ms
64 bytes from 192.168.1.1: icmp_req=22 ttl=64 time=0.664 ms
64 bytes from 192.168.1.1: icmp_req=23 ttl=64 time=0.702 ms
64 bytes from 192.168.1.1: icmp_req=24 ttl=64 time=0.699 ms
64 bytes from 192.168.1.1: icmp_req=25 ttl=64 time=0.651 ms
64 bytes from 192.168.1.1: icmp_req=26 ttl=64 time=1.13 ms
64 bytes from 192.168.1.1: icmp_req=27 ttl=64 time=9.90 ms
64 bytes from 192.168.1.1: icmp_req=28 ttl=64 time=0.667 ms
64 bytes from 192.168.1.1: icmp_req=29 ttl=64 time=0.686 ms
64 bytes from 192.168.1.1: icmp_req=30 ttl=64 time=0.700 ms
64 bytes from 192.168.1.1: icmp_req=31 ttl=64 time=0.834 ms
64 bytes from 192.168.1.1: icmp_req=32 ttl=64 time=0.730 ms
64 bytes from 192.168.1.1: icmp_req=33 ttl=64 time=0.713 ms
64 bytes from 192.168.1.1: icmp_req=34 ttl=64 time=0.720 ms
64 bytes from 192.168.1.1: icmp_req=35 ttl=64 time=0.685 ms
64 bytes from 192.168.1.1: icmp_req=36 ttl=64 time=0.682 ms
64 bytes from 192.168.1.1: icmp_req=37 ttl=64 time=0.724 ms
64 bytes from 192.168.1.1: icmp_req=38 ttl=64 time=0.848 ms
64 bytes from 192.168.1.1: icmp_req=39 ttl=64 time=7.04 ms
64 bytes from 192.168.1.1: icmp_req=40 ttl=64 time=0.711 ms
64 bytes from 192.168.1.1: icmp_req=41 ttl=64 time=1.04 ms
64 bytes from 192.168.1.1: icmp_req=42 ttl=64 time=0.678 ms
64 bytes from 192.168.1.1: icmp_req=43 ttl=64 time=0.671 ms
64 bytes from 192.168.1.1: icmp_req=44 ttl=64 time=0.668 ms
64 bytes from 192.168.1.1: icmp_req=45 ttl=64 time=0.682 ms
64 bytes from 192.168.1.1: icmp_req=46 ttl=64 time=0.687 ms
64 bytes from 192.168.1.1: icmp_req=47 ttl=64 time=0.702 ms
64 bytes from 192.168.1.1: icmp_req=48 ttl=64 time=0.778 ms
64 bytes from 192.168.1.1: icmp_req=49 ttl=64 time=1.03 ms
64 bytes from 192.168.1.1: icmp_req=50 ttl=64 time=0.678 ms

--- 192.168.1.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 50425ms
rtt min/avg/max/mdev = 0.629/1.061/9.900/1.545 ms
[mmmmna@localhost ~]$

The data for icmp_req #27 and #39 was generated at the same time when I deliberately clicked to preview my post, just to show how my own traffic can change the results.

Thanks to everyone for all the help, things are much better now, have been decent since I A] returned to using OpenDNS and B] disabled IPV6 in Firefox. The Firefox tweak is definitely a classic adjustment that needs to be made, and is an adjustment which I tend to forget to make when I overwrite an older distro installation.

[AS]

Thanks to everyone for all the help, things are much better now, have been decent since I A] returned to using OpenDNS and B] disabled IPV6 in Firefox. The Firefox tweak is definitely a classic adjustment that needs to be made, and is an adjustment which I tend to forget to make when I overwrite an older distro installation.

Good that things has improved. Still I'm thinking at something else because of:

[mmmmna@localhost ~]$ time -p ping -c 1 www.google.com
PING www.l.google.com (74.125.230.113) 56(84) bytes of data.
64 bytes from 74.125.230.113: icmp_req=1 ttl=57 time=92.5 ms

--- www.l.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 92.521/92.521/92.521/0.000 ms
real 5.34
user 0.00
sys 0.00

the above times are completely independent from Firefox settings.

AS

[mmmmna]

Well, I'm quite happy to report that I rarely get long delays now that I have disabled IPV6 in the 2 locations (in Firefox and in network configuration settings).

Still wondering how well things would work if I had my own DNS cache, but the need isn't as urgent.

Also still wondering if using IPV6 within (and on) an IPV6 network will remain as slow as I had been reporting in April. That would be sensational, if a simple DNS lookup took several seconds in a normal IPV6 future.

[YouCanToo]

Well, I'm quite happy to report that I rarely get long delays now that I have disabled IPV6 in the 2 locations (in Firefox and in network configuration settings).

Still wondering how well things would work if I had my own DNS cache, but the need isn't as urgent.

Also still wondering if using IPV6 within (and on) an IPV6 network will remain as slow as I had been reporting in April. That would be sensational, if a simple DNS lookup took several seconds in a normal IPV6 future.

I really do not believe that you will see any stellar performance from using it.

[sling-shot]

Sounds to me like an IPv4/IPv6 problem.

I would ensure that IPv6 is disabled in FF if not in use.

Under about:config

network.dns.disableIPv6;                 true

Just posting to say that this has greatly improved my life
Thanks to you and also to mmmmna for starting this thread.
-SS.