One or more of your nameservers did not return any of your NS records!

SajtXL

Verified User
Joined
Nov 12, 2006
Messages
88
The company I hired my VPS seems to have gone bankrupt?
So now I try to quickly bring up a new VPS, everything looks good apart from this - for me - difficult (and acute DNS problem, I hope that some kind soul is able to assist here.

Here are the report from intodns ( http://www.intodns.com/sajtxl.com )

Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.
Error DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not responded are: 89.238.174.151 89.238.174.152

I have looked around in every place, i think, any ides ?

I have this entry under DNS control:
ns1.sajtxl.com. A 89.238.174.151
ns2.sajtxl.com. A 89.238.174.152

sajtxl.com. NS ns1.sajtxl.com.
sajtxl.com. NS ns2.sajtxl.com.

And from "nameservers"
89.238.174.151 shared 10 ns1.sajtxl.com
89.238.174.152 shared 0 ns2.sajtxl.com

and from var/named/
$TTL 14400
@ IN SOA ns1.sajtxl.com. hostmaster.sajtxl.com. (
2010110106
14400
3600
1209600
86400 )

sajtxl.com. 14400 IN NS ns1.sajtxl.com.
sajtxl.com. 14400 IN NS ns2.sajtxl.com.

ftp 14400 IN A 89.238.174.150
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 89.238.174.150
ns1.sajtxl.com. 14400 IN A 89.238.174.151
ns2.sajtxl.com. 14400 IN A 89.238.174.152
pop 14400 IN A 89.238.174.150
sajtxl.com. 14400 IN A 89.238.174.150
smtp 14400 IN A 89.238.174.150
www 14400 IN A 89.238.174.150

In advance, thanks for your time.
 
I tried a test:
Code:
$ dig @89.238.174.151 sajtxl.com

; <<>> DiG 9.7.0-P1 <<>> @89.238.174.151 sajtxl.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
If you know your named daemon is running on your server then you need to check firewalling, since the outside world can't get a response from your nameserver. For DNS to work you have to allow both inbound and outbound traffic on port 53, both UDP and TCP/IP.

Jeff
 
Thank you Jeff...

Yes, thats correct, the port 53 was blocked...
DA Support guide me to switch it off.

Thanks

/ Gunnar
 
Note to everyone: by default, CentOS and Red Hat firewall installations block port 53.

I can't speak for the others; while we maintain them, we don't install them from bare metal.

Jeff
 
Back
Top