Unable to use DirectAdmin servers name servers

[youds]

Hi

MY namservers aren't working. I configured the domains NameServers to the IP address of the server DirectAdmin has the IP of but its just not working, I get these error messages:
Failed to find name servers of youds.com/IN.
No name servers found at child.
No name servers could be found at the child. This usually means that the child is not configured to answer queries about the zone.

Strange this is i have ns1.youds.com assigned in Administrator settings and a name server registered under name servers in reseller panel. Im a bit stuck.

This domain is youds.com

 

[youds]

So far I have deleted the name servers (i think this is defy a DA support issue) by going to IP Manager and clearing the name servers, I couldn't delete the name servers from the Resellers Nameserver page. I then went back to the Nameservers page in the Reseller account and indeed the entry had gone. Thank god ! So I added virtual name servers worked ok, and then it added the domain ns1.youds.com to the ip and gave a warning about the second ip in ns2.youds.com. Unfortunately this did not work.

 

[youds]

At the IP Registrar:
Zone File

$ORIGIN youds.com.
$TTL 1800
youds.com. IN SOA ns1.digitalocean.com. hostmaster.youds.com. 1437139229 10800 3600 604800 1800
youds.com. 1800 IN NS ns2.youds.com.
youds.com. 1800 IN A 178.62.42.232
youds.com. 1800 IN NS ns1.youds.com.

 

[Richard G]

I don't understand what you are trying to do. According to the screenshots I see 4 nameservers with the same ip address.

You got some problems, since you are using only 1 ip for both nameservers.
Check this:
http://www.intodns.com/youds.com

It seems your nameservers are set to 88.208.229.2 and in your screenshots you are using a 178.x.x.x ip address.
So you have an issue at your registrar. Set the ip's for the nameservers correctly there to begin with.

 

[DirectAdmin Support]

Manually testing the server, I'm not getting any response:

[root@server ~]# dig youds.com @88.208.229.2

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> youds.com @88.208.229.2
;; global options: +cmd
;; connection timed out; no servers could be reached

which probably means either there is a firewall blocking port 53 (tcp+udp) or named isn't running.




Is named running? If it is, try doing that manual test locally on the server to see what you get.

John

 

[youds]

Manually testing the server, I'm not getting any response:

[root@server ~]# dig youds.com @88.208.229.2

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> youds.com @88.208.229.2
;; global options: +cmd
;; connection timed out; no servers could be reached

which probably means either there is a firewall blocking port 53 (tcp+udp) or named isn't running.




Is named running? If it is, try doing that manual test locally on the server to see what you get.

John

[root@europa scripts]# dig youds.com

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2 <<>> youds.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 46156
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

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

;; Query time: 3022 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Fri Jul 17 22:55:19 2015
;; MSG SIZE  rcvd: 27

[root@europa scripts]# dig youds.com @88.208.229.2

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.2 <<>> youds.com @88.208.229.2
;; global options: +cmd
;; connection timed out; no servers could be reached
[root@europa scripts]#

Why do you specifically mention 88.208.229.2? its 178.62.42.232 what should be the sole IP address. Sorry I included some screenshots from another thread stupid forums.

when I try to create Glue records at OVH all I get is:
You should declare at least a 'A' field on your dns zone for hostname ns1.youds.com in order register this hostname on each registries

IF one more person tells me to add A records I will go nuts? Do I not have these already?

 

[youds]

See the attached image

 

[DirectAdmin Support]

88.208.229.2 is because that's what's set at the registrar:
Nameserver records returned by the parent servers are:

ns1.youds.com. ['88.208.229.2'] [TTL=172800]
ns2.youds.com. ['88.208.229.2'] [TTL=172800]

so that's where public dns lookup servers (eg google's at 8.8.8.8/8.8.4.4) would be looking, so we're basically going right to the source.

If that's not the correct IP, then you'd need to fix that at your regstrar.
Change the "host" values for ns1/ns2 to resolve to the correct IPs by logging into your registrar (not a setting for the DA box)

When I manually query 178.62.42.232 directly, it works perfectly.

John

 

[Richard G]

Yep, that's what I also said before. He has to change the ip at his registrar to the correct nameserver ip's.