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.
Sometimes it takes up to 30 secs to resolve the names, I'm using Firefox on OpenSuse 10.2 64 bit. No problem to ping manually any of the websites I'm trying to access.
I checked that the IPs of my ISP's Name Servers are correct in /etc/resolv.conf and I also tried to switch between the 1st and the 2nd one but with no effect.
also another approach could be to install dnsmasq or even squid so that you don't need to do so many dns lookups... i remember i had an ISP before with sucky DNS servers and installing dnsmasq locally (as in on the same desktop running firefox) made a huge difference... of course this assumes the problem is on the server side... you can confirm the problem occurs even with your firewall turned-off, right?? what kinda connection do you have?? also, what does a ping look like with your DNS servers??
do a traceroute against your dns server so you can find out where it gets slow and report the problem to your ISP with some documentation and examples over time.
4.2.2.1 to 4.2.2.6 are public DNS servers that can be used during troubleshooting to verify Internet connectivity. I use them very often, especially when I am in an unfamiliar network and would rather not use the DNS services they provide.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.