Help! One or more of your nameservers did not respond

M

Mitya1987

Verified User
Joined
Aug 23, 2021
Messages
19
Hello community, I have a problem with dns, it gives this error. ( ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
89.208.211.234) I am a newbie, if there are experts tell me what to do. I will give all data to analyze this error.
Domain for check myserver.moscow. https://intodns.com/myserver.moscow
 
Check that you have port 53 incoming and outgoing open in udp and tcp.

Also check if your named.conf is correct, use this example:

Is this named.conf correctly configured?

Hi guys i'm trying to configure my own custom nameservers on my DA server but i dont know if i'm configuring it good The lines on the named.conf file are ok? named.conf My server have Centos 7 Thanks in advance
forum.directadmin.com forum.directadmin.com

and check if your nameservers are setup correctly in Directadmin itself.
 
Richard G said:
Check that you have port 53 incoming and outgoing open in udp and tcp.

Also check if your named.conf is correct, use this example:

Is this named.conf correctly configured?

Hi guys i'm trying to configure my own custom nameservers on my DA server but i dont know if i'm configuring it good The lines on the named.conf file are ok? named.conf My server have Centos 7 Thanks in advance
forum.directadmin.com forum.directadmin.com

and check if your nameservers are setup correctly in Directadmin itself.
Click to expand...
[root@host ~]# netstat -an | grep \:53 | grep LISTEN
tcp 0 0 89.208.211.234:53 0.0.0.0:* LISTEN
tcp 0 0 89.208.209.175:53 0.0.0.0:* LISTEN
tcp 0 0 10.0.0.6:53 0.0.0.0:* LISTEN
tcp 0 0 10.0.1.13:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN


Named

options {
allow-transfer { none; };
//listen-on port 53 { 127.0.0.1; };
//listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
recursing-file "/var/named/data/named.recursing";
secroots-file "/var/named/data/named.secroots";
//allow-query { any; };
 
You're using a home system? Sorry, no experience with that. But seems somewhere the port is not open.
Maybe router forward or something else (firewall).

I also miss the "allow recursion" line, but that might not be the issue in this case.
 
Yes, the virtual machine is in a large data center I have full access to firewall seems to need to open access to internal ports.
 
You would want to check your firewall, it seems that port 53 is not opened on your IP 89.208.211.234
 
Go to your firewall and check if port 53 is open for UDP for 0.0.0.0/0

How exactly to do that - refer to your datacenter Firewall
 
DanielP said:
Go to your firewall and check if port 53 is open for UDP for 0.0.0.0/0

How exactly to do that - refer to your datacenter Firewall
Click to expand...
Hi, I already did this, the data center says that they do not block port 53. I had moments when I changed the rules but the port then closed itself again. Does it open but then close itself?
 
Mitya1987 said:
Hi, what exactly should I check, I'm new to this business!
Click to expand...
As DanielP said, check with your datacenter, contact their support to test.
Telnet from outside (for example form your home ip) to port 53 on your server, you can see if it's closed or not.
What are these doing in your config?
Code: 
tcp        0      0 10.0.0.6:53             0.0.0.0:*               LISTEN
tcp        0      0 10.0.1.13:53            0.0.0.0:*               LISTEN
these are internal private ip's so I'm wondering why they are listening at port 53?

Ports do not close themselves. Unless you have double firewall.
If you have csf/lfd installed then you have to disable the OS firewall like in Centos 8 that is firewalld.
 
You must log in or register to reply here.
Back
Top