Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Here's the issue, any DNS that needs to be resolved ie. google.com takes between 15-60 seconds, and sometimes just simply fails. When going to the IP itself it is fast, like it should be. Downloads are fullspeed as well, as soon as resolving is done.
I used ndis-wrapper to install my motorola WPCI810G PCI card, which worked perfectly. I'm connecting to a motorla WR850G router. And distro I'm on is Mandrake 10.
Here's some info I've gathered that may help.
Settings in Manage Connections - wlan0 (Mandrake Control Center 10)
-------------------------------------------------------------------
DHCP Selected
The slow resolving has happened with konquerer, firefox browsers... and chat programs: x-chat, kopete. Basically I used anything where the DNS resolves as quick as it should. As far as in the router, yeah DNS or traceroute in the router works just fine.
Output from Resolv.conf
---------------------------------
nameserver 192.168.10.1
search localhost
Output from dig www.linuxquestions.org
------------------------------------------------------
;; Query time: 3 msec
;; SERVER: 192.168.10.1#53(192.168.10.1)
;; WHEN: Sun Aug 8 17:10:09 2004
;; MSG SIZE rcvd: 56
NOTE: Browser was at www.linuxquestions.org when dig was done... I just tried dig wwwgoogle.com, and it wouldn't go through, says no servers chould be reached.
UPDATE: okay, so dig www.google.com finally worked.. it's taking between 240-300 msec to resolve... that isn't very long is it?
It looks like your dns server is also your router. Does your router keep a dns table or something? If it does you may need to flush it or something. also try to do and nslookup on an address and see what dns address your really using and how long it takes.
what is the effect of removing the line search localhost from resolv.conf? I had problems in the past with similar entries so I removed them. I have a router too and I use the address of the router as my nameserver and I have no problems whatsoever.
Originally posted by DevilDust btw, I tried putting in ISP nameservers, that I took from working Windows machine like:
nameserver 192.168.10.1
nameserver isp nameserver 1 (the IPs, i forgot them)
nameserver isp nameserver 2
didn't seem to matter much, maybe i should take out the router ip as nameserver.. and just put isp nameservers back in?
That wouldn't matter because it would search for the entries at 192.168.10.1 before going to nameserver 1 and 2. Put nameserver 1 first and see if the times improve.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.