[solved]Slow dns lookup from terminal -- normal speed in firefox ???

firecat53 · 2009-06-02 04:19:40

Strange problem for last few weeks. DNS lookups while in terminal are very slow (e.g. pacman has a normal download speed, but pauses in between each download, and it takes forever for yaourt to check each AUR package, and elinks even has long pauses anytime you go to a new address). Firefox browses normally -- even to brand new sites that aren't cached. Download speeds are normal -- it's just the lookup time. I had the same issue in firefox, too until I globally disabled IPv6 per the wiki (modprobe.conf entry).

I just don't get why it would be different between firefox and terminal (both virtual terminals and urxvt respond the same way) !

/etc/hosts:
127.0.0.1               scotty.localdomain      localhost scotty
192.168.1.100   mediacenter
192.168.1.101   homeserver
192.168.1.102   familyroom
192.168.1.1     router

/etc/network.d/profile
CONNECTION="wireless"
ESSID="firecat4153"
INTERFACE="wlan0"
DESCRIPTION="Automatically generated profile"
IWCONFIG="rate 54M mode managed"
SCAN="yes"
IP="static"
IFOPTS="192.168.1.104 netmask 255.255.255.0 broadcast 192.168.1.255"
GATEWAY="192.168.1.1"
DNS1="192.168.1.1"
TIMEOUT="10"
SECURITY="wpa"
KEY="key"

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0

 /etc/resolv.conf
nameserver 192.168.1.1

Let me know if I can provide any other info for troubleshooting.

Thanks!
Scott

Last edited by firecat53 (2009-06-05 03:37:24)

fukawi2 · 2009-06-02 05:16:50

dig google.com
dig google.com @192.168.1.1

Gen2ly · 2009-06-02 11:40:01

ftp.archlinux.org gets pretty busy and queries go through there?

foutrelis · 2009-06-02 15:43:57

Highly unlikely, but make sure that you're not using a proxy (which would explain the slowness):

echo $http_proxy

firecat53 · 2009-06-02 17:04:48

Well, it appears its a problem with my router -- I'm not sure what yet. I went to work today and the wireless connection at work connects perfectly both through the terminal and firefox. All the lookups are apparently normal and speedy! I did check $HTTP_PROXY and $htttp_proxy, both are null. I will have to get home before I try the dig commands -- it all works great here! If it is my router, what the heck could cause that difference?? Oh well, I'll try it tomorrow and see what pops up.

Thanks,
Scott

firecat53 · 2009-06-04 17:32:38

dig google.com
dig google.com@192.168.1.1

[firecat53@scotty ~]$ dig google.com

; <<>> DiG 9.6.0-P1 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16711
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             240     IN      A       74.125.67.100

;; Query time: 36 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jun  4 10:31:15 2009
;; MSG SIZE  rcvd: 54

[firecat53@scotty ~]$ dig google.com @192.168.1.1

; <<>> DiG 9.6.0-P1 <<>> google.com @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7066
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             240     IN      A       74.125.67.100

;; Query time: 7 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jun  4 10:31:25 2009
;; MSG SIZE  rcvd: 54

Does that shed any light? I'm not much of networking guru.

This is baffling me!! I don't understand why there would be a difference between internet from terminal and internet from a gui browser!! Anyone have any brilliant insights?? Please??

Thanks!
Scott

Last edited by firecat53 (2009-06-04 17:34:38)

fukawi2 · 2009-06-04 23:18:36

WARNING: recursion requested but not available

Something is not quite right -- your router should be happy to offer you recursion. It says that it won't, but then it does (by resolving Google for you)

This could be part of your problem. Is this an off-the-shelf product, or a home-built firewall/router?

Last edited by fukawi2 (2009-06-04 23:19:16)

firecat53 · 2009-06-05 01:40:25

Well, I've done some more testing:
Ubuntu, mint and arch (about 3 or 4 months old larch usb flash drive) booted on this computer all work perfectly. 'elinks google.com' brings it up almost instantly, aptitude and pacman updates hook up immediately to the servers. 'elinks google.com' right now (64 bit arch - all up to date) takes almost 10 seconds to resolve the hostname, pacman and wget take 5-10 sec to start a download.

I have two other arch32 machines in the house, and they both also are experiencing this lag from the command line. But again, firefox browsing works great -- no lag.

@fakawi2 - the router is a linksys wrt54-G2. And now given that other distros seem to work fine, I'm thinking it's not the router. But then my laptop worked fine on a different network!!

Thanks,
Scott

cactus · 2009-06-05 03:03:40

if you have any zeroconf or samba crap (wins) going on, it could be screwing things up (upnp on your router)

http://bbs.archlinux.org/viewtopic.php?id=58712

anyway, try some of the solutions posted there and see if any help.

Last edited by cactus (2009-06-05 03:05:14)

firecat53 · 2009-06-05 03:36:39

Well, I think I solved it, although I don't quite understand....
With my old Dlink router, my resolv.conf just had the router as the nameserver (nameserver 192.168.0.1).
With this new WRT54G2 router, that seems to not work, and the resolv.conf needs to have actual DNS servers (I use the Open DNS servers) in it. Just having the 192.168.1.1 address seems to be the problem. That's why when I connected with Wicd or network manager or even using automatic DHCP instead of the static IP I'm using now, that it would work properly, because the resolv.conf would be updated automatically with the other DNS servers.

Anyway, all better now. Although feel free to chime in if you can explain why this would affect the terminal but firefox worked fine

Thanks!
Scott

Last edited by firecat53 (2009-06-05 03:49:40)

Gen2ly · 2009-06-06 21:45:23

Yeah think this relates to the new dhcpcd? Before the update I too just used '208.67.222.222' for example and it did fine. Prepending that with nameserver fixed it.

Arch Linux

#1 2009-06-02 04:19:40

[solved]Slow dns lookup from terminal -- normal speed in firefox ???

#2 2009-06-02 05:16:50

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#3 2009-06-02 11:40:01

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#4 2009-06-02 15:43:57

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#5 2009-06-02 17:04:48

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#6 2009-06-04 17:32:38

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#7 2009-06-04 23:18:36

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#8 2009-06-05 01:40:25

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#9 2009-06-05 03:03:40

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#10 2009-06-05 03:36:39

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

#11 2009-06-06 21:45:23

Re: [solved]Slow dns lookup from terminal -- normal speed in firefox ???

Board footer