ERROR: One or more of your nameservers did not respond

A

Anurag M

Verified User
Joined
Apr 10, 2020
Messages
14
Hello everyone.
I am new to this server stuff. I am trying to setup my dedicated server with directadmin to run a domain. (indiafollow.com).
Dedi is from OVH. it has (1+16 Ips)

So here is what I have done:
  1. Installed Centos7 and Directadmin in my server. 1586503718976.png
  2. Added extra IPs to the server1586503747164.png
  3. Added the IPs to nameservers in directadmin from reseller level 1586503856728.png
  4. Created nameservers in domain registrars panel and added A entries to nameservers and hostname both1586503952121.png1586503977116.png
  5. Created a new account with "indiafollow.com" domain name in directadmin.

The result can be seen here: https://intodns.com/indiafollow.com

Please tell me what I did wrong or missed.
 
IndiaFollow said:
Created a new account with "indiafollow.com" domain name in directadmin.
Click to expand...
Check if this one also has the correct NS records en A records for the nameservers.

If not, go to reseler level of admin,
"Set the Nameservers that will be assigned to new users" see that both are correct and click save. After that, check domain again.
 
Nameservers are correctly set for the domain
1586544610535.png

from Admin level, if I go to DNS Administration it looks like this. don't know if its correct or not.

1586544705612.png
 
Your domain can not be found at the moment.
Firstly, you have a bunch of duplicate entry's. Remove the duplicates and leave the ones you are really working with.

For example.... You have 3 A records for indiafollow.com, no wonder DNS is going crazy. Remove 2 of them.
Same for pop, smstp, www, ftp and mail. Remove them all except 1 entry for each, pointing to your main server ip so I guess 51.75.105.160.

Check if named is running, because at the moment I can't even do an nslookup to ns1.indiafollow.com I get a timeout.
Also be aware to have port 53 TCP/UDP open (incoming and outgoing) in your firewall.

Most important.... have a look here. Your ns1.indiafollow.com and ns2.indiafollow.com are pointing to the wrong ip adresses.
 
Also IPs for NS must be equal at domain registar and at Directadmin DNS side, now at "step 4", and at last screen - You have different values.
 
Richard G said:
Most important.... have a look here. Your ns1.indiafollow.com and ns2.indiafollow.com are pointing to the wrong ip adresses.
Click to expand...

Zhenyapan said:
Also IPs for NS must be equal at domain registar and at Directadmin DNS side, now at "step 4", and at last screen - You have different values.
Click to expand...

Yes, I saw they have wrong IP. I will change them and have a look, but every account I create is having the same wrong IPs. I don't suppose I will have to change every accounts DNS manually when I create a new one? There must be a way to solve this in directadmin settings. I don't know what I am missing!
 
All created accounts will have IP that You assigned to them (resellers default IP/or servers default IP/or that You set manually when configuring account) and have NSs that defined at reseller level. Check Your configuration attentively.
 
Most easy way. Temporarily change to the enhanced theme and then take/check these steps:

Understand DNS

I've a fresh DA instalation and i want to configure nameservers. In my server i have 2 IP, when installing DA take primary IP for license issue and take this for primary IP for create domains cool here. The problem i've i want to "custom" ns1 and ns2 because DA take primary IP and assing IP...
forum.directadmin.com forum.directadmin.com

Then remove wrong nameservers from existing domains.

It's like Zhenyapan says.
 
Ok. So I am once again trying with a simple approach. I have removed all the other IPs from the server. So it has now only 1 IP. The same IP I have set for ns1 ns2 and hostname in domain registrar panel.

Added the domain in directadmin.
Here are the DNS records for the domain

1586881625137.png

Can you guys tell me what am I missing?
 
Now I'm getting confused.
At first you used the ip with 51 in the beginning, also for your nameservers. Only the two 188 ip's were wrong.
And now suddenly your using the 188 ip for everything? Including nameservers? So now I'm confused.

Since the beginning you used 3 ip's. The 2 starting with 51 and 1 starting with 188. I can't help you like this if you keep changing ip adresses on your server.

Now what is your main server ip and what is the additional ip installed on your server,

Then tell me which ip's you have designated as your registrar for nameserver ip's.
 
Ok. Sorry. Reverted them to old settings.
  • As you said, I got rid of the other 'A' entries.
  • Added A records for the NS1, NS2 with IP addresses 51.75.105.160 and 51.75.105.161
  • Added A record for hostname (alpha.indiafollow.com) with IP Address 188.165.252.227. - This is the main server IP.
  • Custom name servers (ns1.indiafollow.com, ns2.indiafollow.com) created in domain registrar end with IP address 51.75.105.160 and 51.75.105.161
Here is the DNS settings for domain name "indiafollow.com" in directadmin.

1587190893714.png


Here is the DNS settings for domain name "indiafollow.com" in domain registrar end.

1587191063469.png

Here is the IP allocation for nameservers in DA (Reseller level) and default nameservers for new users.
1587191195418.png

NS Records and A records both are present for the nameservers. But I can't ping the nameservers. IPs that I have assigned to them are pinging though.
 
It looks like port 53 is closed for the server. Can that be a reason for this? if yes, How do I resolve this?

1587205375760.png
 
I figured it out finally!
The following lines were commented out in the file "/etc/named.conf" for some reason.

Code: 
// listen-on port 53 { any; };
// listen-on-v6 port 53 { ::1; };

Removed the "//" and restarted "named" using

Code: 
service named restart
 
Those lines are commented out by default after DA installation.
Normally they don't need to be removed. You were looking at the wrong ip. You should but those // back and restart named again.

In one of the previous reply's of you it said:
"port 53 is closed on 188.165.252.227" which is correct.
Because your nameservers are not on that ip, your nameservers are on the 51.75.xx.xx ip adresses. So on those ip's should have port 53 open.
Not the 188 ip because there is no nameserver running on thaa ip, so should be closed. ;)
 
You must log in or register to reply here.
Back
Top