[SOLVED] dig localhost doesn't give the answer section
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 trying to setup a DNS server on centos. My problem is that when I try to do dig google.com it works... but when i hit dig localhost it doesn't give the answer section also nslookup doesn't give the output.
fwiw, on my centos 6.5 server that's successfully running bind, dig localhost doesn't return an answer either. I think localhost is normally defined in your /etc/hosts file not in the dns server.
fwiw, on my centos 6.5 server that's successfully running bind, dig localhost doesn't return an answer either. I think localhost is normally defined in your /etc/hosts file not in the dns server.
not necessarily, can be either in /etc/hosts or in a zone file, with forward zone A record of hostname "localhost" mapped to 127.0.0.1
I had the same problem when I first tried to set it up on a CentOS box. Comes out that the culprit was SELinux. Turn off the SELinux temporarily and then try to 'dig' localhost to see if that works.
Sorry for the late reply..... was out of town for some days...
I checked and found out that i forgot to configure iptables. port 53 is not allowed by iptables by default, we have to change the configuration of iptables for it.
did the necessary changes and bam...!!! everything was working smoothly....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.