does not answer queries over tcp and udp in name sever(centos)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
does not answer queries over tcp and udp in name sever(centos)
Well online dns test shows that the following :
Code:
Name server ns0.x.com (xxx.xxx.xxx.x) does not answer queries over UDP.
The name server failed to answer queries sent over UDP. This is probably due to the name server not correctly set up or due to misconfigured filtering in a firewall.
Name server ns0.x.com (xxx.xxx.xxx.x) does not answer queries over TCP.
The name server failed to answer queries sent over TCP. This is probably due to the name server not correctly set up or due to misconfgured filtering in a firewall. It is a rather common misconception that DNS does not need TCP unless they provide zone transfers - perhaps the name server administrator is not aware that TCP usually is a requirement.
So can anyone tell me what does that mean and what should be done?Actually ns0 is used for zone transfer only,doe real dns purpose other dns server(ns1 an dns2) is used and that doesnt show sch error.
However ns3 show that error but with tcp...
Therefore can anyone help me on this or give ay idea or suggestion?
since you don't specify which OS and BIND you are running on your server (if I recall from my memory you previously asked for CentOS help @ LQ)
you should first configure your server's BIND (DNS) settings for that domain you are authoritative (you control it's IP addresses).
.....
Actually ns0 is used for zone transfer only,doe real dns purpose other dns server(ns1 an dns2) is used ...
....
I'm sorry I didn't quite well understand your question.
- what online dns test ?
can you provide a link ?
- ns0 is used for zone transfer ...?
Transferring zones from where to ?
If it's somehow only a rsync set on this server to transfer (only my guess what it is), then it's not configured for DNS and that means that the server which handles your domain should have take care of that
No,the bind has been correctly configured and it's a live server..it has centos 5.8 running..We are ISP.
well i checked for our domain at http://dnscheck.pingdom.com and there it showe the errors as said above. And what i meant previously was ns0 is not used for resolving names,dat is done by slave servers.
So is it ok even if udp and tcp is blocke/filtered as ns0 is not used for resolving names.
And i wanted to know what that error meant.
No,the bind has been correctly configured and it's a live server..it has centos 5.8 running..We are ISP.
well i checked for our domain at http://dnscheck.pingdom.com and there it showe the errors as said above. And what i meant previously was ns0 is not used for resolving names,dat is done by slave servers.
So is it ok even if udp and tcp is blocke/filtered as ns0 is not used for resolving names.
And i wanted to know what that error meant.
well, that explains it all.
If it's not name resolver then it shouldn't response to DNS queries (resolving).
The error is probably because of the settings for your domain at the master DNS server,
which may have configured
ns0.domainname.com
as a primary DNS for the domain.
As I can assume you have ns1 as primary domain server so it should be changed on TOP LEVEL domain registrar to point to ns1... not ns0.
And domain querying is actually running through UDP port 53 and not TCP (rarely I've seen it, I can't remember which it was).
whatewa, I can presume it is a master DNS server so you should then configure it to respond to DNS queries,
or if you do not want to have it respond to queries (for whichever reason that you have), then leave it to slaves, as you have it now (but you could have trouble resolving your domain - eg. example.com).
You can check it here if your domain is configured properly.
oh ok thanks..that means it's ok even if the master doesn't reply to the queries if slave is doing that..
And ya i checked it in the link u provided and everything looked good except the dns part where it said that the ns0 isn't replying to the queries..so i suppose that's good hopefully..
And ya i was using English language only,sorry about those shortcuts as I'm used to it..haha...will try to avoid it from next time..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.