Name server configuration

How long ago did you change the nameserver and glue records? It doesn't look like you misconfigured something. Although I would never use the same ip for 2 nameservers.
Is port 53 on your firewall open and named running? It seems your nameserver is not responding to request.
IntoDNS is a better tool to check you DNS, you can see that the nameserver is not responding.
http://www.intodns.com/youds.com
 
About 2 days ago now.

See below.

Code: 
$ dig youds.com @164.132.200.239

; <<>> DiG 9.8.3-P1 <<>> youds.com @164.132.200.239
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8836
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;youds.com.			IN	A

;; ANSWER SECTION:
youds.com.		14400	IN	A	164.132.200.239

;; AUTHORITY SECTION:
youds.com.		14400	IN	NS	ns2.youds.com.
youds.com.		14400	IN	NS	ns1.youds.com.

;; ADDITIONAL SECTION:
ns1.youds.com.		14400	IN	A	164.132.200.239
ns2.youds.com.		14400	IN	A	164.132.200.239

;; Query time: 20 msec
;; SERVER: 164.132.200.239#53(164.132.200.239)
;; WHEN: Thu Aug 18 02:27:21 2016
;; MSG SIZE  rcvd: 111

Code: 
[root@neptune ~]# service named status
Redirecting to /bin/systemctl status  named.service
● named.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/etc/systemd/system/named.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2016-08-03 13:26:01 CEST; 2 weeks 0 days ago
  Process: 1769 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
 Main PID: 26349 (named)
   CGroup: /system.slice/named.service
           └─26349 /usr/sbin/named -u named

Aug 18 03:01:30 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 193.0.9.6#53
Aug 18 03:01:31 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 62.219.128.128#53
Aug 18 03:01:31 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Aug 18 03:01:44 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 212.179.7.7#53
Aug 18 03:01:44 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 193.0.9.6#53
Aug 18 03:01:44 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 62.219.128.128#53
Aug 18 03:01:45 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '138.95.219.62.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Aug 18 03:19:09 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '239.218.141.86.in-addr.arpa/PTR/IN': 193.0.9.6#53
Aug 18 03:19:09 neptune.youds.com named[26349]: error (unexpected RCODE SERVFAIL) resolving '239.218.141.86.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Aug 18 03:25:20 neptune.youds.com named[26349]: client 86.141.218.239#51766 (yous.com): query (cache) 'yous.com/A/IN' denied
 
Your nameserver is not resolving now. Looks like no RDNS or glue record present.
Did you point to your nameservers at your registrar of youds.com?
 
Apparently its because I am using the same IP address, i have bought a second IP will see how that goes down.
 
Hi,

can you check again for me, it seems the error is suggesting my name servers are not responding authoritatively. See http://www.intodns.com/youds.com.

I don't know what I can do to get them to respond; and yes my settings at the registrar are all 100% spot on, see screenshots.

Screen Shot 2016-08-18 at 19.10.16.png
Screen Shot 2016-08-18 at 19.10.20.png
 
Hello,

It seems to be working at least from my end:
Code: 
$ dig SOA youds.com @164.132.200.239 +short
ns1.youds.com. hostmaster.youds.com. 2016081801 14400 3600 1209600 86400

$ dig SOA youds.com @178.32.50.141 +short
ns1.youds.com. hostmaster.youds.com. 2016081801 14400 3600 1209600 86400
 
That way you can only detect if it is working locally on his server, it still is not resolving from other servers

Only from 1 server I'm able to get resolving results. But the domain name and www will still not resolv so there is still something wrong.
Code: 
dig -t NS youds.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.8 <<>> -t NS youds.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20643
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;youds.com.                     IN      NS

;; ANSWER SECTION:
youds.com.              80807   IN      NS      ns1.youds.com.
youds.com.              80807   IN      NS      ns2.youds.com.

However, why such enormous high timeout setting of 80807? Why not the default 14400? I would change that if I were you.

This is from the same server:
Code: 
#nslookup ns1.youds.com

Non-authoritative answer:
Name:   ns1.youds.com
Address: 164.132.200.239

but then.....
nslookup youds.com or www.youds.com will get a servfail.

It looks good in the screenshots at the registrar so at the moment I don't know where exactly the problem is. Unless there is something not working correctly at our registar or the datacenter maybe?
 
Or maybe in Directadmin because the ns1 en ns2 are resolving (at least at one of my servers) and the www and non-www domain name is not.
I would at least start with changing the value of DNS back to default value of 14400.

Changed this line of text, port 53 is working now so firewall is ok too.
 
Last edited:
So I've waited some days because some servers were responding and others weren't, to no avail. I'm going to escalate this with OVH when they get back in on Monday, Uvesh the person helping had already done so but I'm sure everything is setup as it was on the old server as all I have done is migrated and left default settings. Which should work right?

Kind regards
 
I just wonder why for example ns1.youds.com does resolve on 1 server. Not even on Google's dns (8.8.8.8) is resolves, still neither on my other servers.
It's very odd and you are correct.
If you have setup everything exactly as on the old server, things should be right.

I don't like the fact that OVH does not work in the weekend. We had a server there for 1 month, got a harddrive defective on saturday and had to wait till monday for replacement. We fastly got back to Hetzner where we got another server. They do support in the weekend by email and they do replace harddisks in the weekend.
Never had such weird DNS problem there luckily.
 
FYI, I tested with +tcp to force tcp rather than udp. Both ns1/ns2 return the domain correctly, so it's a firewall issue where UDP is blocked on port 53, but TCP is open on port 53. The DNS system requires UDP on port 53.

John
 
So; just to continue this debacle, it would appear that port 53 wasn't open however I have since switched to APF and can confirm port 53 is deffo open. Waiting on propagation; I've had the server working fine from OVH's DNS servers so can confirm also that the problem lies somewhere within my DA setup.

Edit: now waiting on emailerapp.com to start working and/or youds.com to stop working so can further diagnose the problem.

Kind regards
 
Last edited:
Also take a look at this it doesn't include any IP address info of mine except the localhost:
Code: 
[root@neptune ~]# cat /etc/resolv.conf
nameserver 127.0.0.1
nameserver 213.186.33.99
search ovh.net
 
since switched to APF and can confirm port 53 is deffo open
Click to expand...
How did you confirm this? And is named running? Because according to intodns both nameservers are still not reachable.
 
You must log in or register to reply here.
Back
Top