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.
I am running a caching nameserver on my linux machine but when i do a nslookup from linux machine the name is resolved very fast and when I do nslookup form a windows machine whose primary name server is my linux machine then the name is resolved to slow and some time it does not resolves from my linux machine and is resolved from my isp name server. here is the output of some important command and configs
windows machine
Code:
C:\Documents and Settings\Asif>nslookup hotmail.com
*** Can't find server name for address 192.168.0.3: Non-existent domain
Server: pathfinder.nexlinx.net.pk
Address: 202.59.80.10
Non-authoritative answer:
Name: hotmail.com
Addresses: 64.4.33.7, 64.4.32.7
The reason it's probably taking so long and spitting out that error is it's trying to do a reverse lookup of the ip address 192.168.0.3. Have you setup your reverse dns for that ip? Since 192.168.x.x is private ip space you will have to setup a local one on your dns server. It should eliminate that error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.