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.
192.168.1.100 is my router... 127.0.0.1 is... well, if you don't know that, leave.
Anyway, it takes 15 seconds to resolve a DNS address in a web browser... It takes 0 seconds to ping something...
[kane@localhost kane]$ ping yourmom.com
PING yourmom.com (64.246.50.9) 56(84) bytes of data.
64 bytes from yourmom.com (64.246.50.9): icmp_seq=1 ttl=46 time=73.7 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=2 ttl=46 time=70.8 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=3 ttl=46 time=84.7 ms
64 bytes from yourmom.com (64.246.50.9): icmp_seq=4 ttl=46 time=71.5 ms
192.168.1.100 is my router... 127.0.0.1 is... well, if you don't know that, leave.
Not the type of wording I would use if I was hoping to generate replies to my question.
Anyway, it takes 15 seconds to resolve a DNS address in a web browser... It takes 0 seconds to ping something...
Obviously a timeout problem of some sort. I know, duh! Have you verified the following?
1) Is there a DNS server running at 127.0.0.1?
2) If yes, are you posiibly restricting query access? i.e. allow-query?
3) Is there a DNS server running at 192.168.1.100?
4) If yes, are you possibly restricting query access? i.e. allow-query?
5) Are you sure your ping results were not using cached results from previous queries?
6) From the host at 127.0.0.1, does the output of "dig yourmom.com a" show proper name resolution without a timeout?
7) How about the other name server you have specified? i.e. dig @192.168.1.100 yourmom.com a
I know the above questions seem basic, but it might at least help pinpoint whether or not this problem is application specific -or- your systems resolver lib config specific. Also, I would think that a web browser running on the same system is calling the same resolver lib utillites that ping uses. i.e. gethostbyname and gethostbyaddr. But then, I haven't looked at the source code.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.