Glued DNS

Timon-TNT

Verified User
Joined
Sep 16, 2013
Messages
18
Hi.
I have installed my DirectAdmin on da.domain.com
I set up two DirectSlave DNS ns1.domain.com and ns2.domain.com on different locations and connection is OK.
On my DNS registrar I pointed my domain.com to my new ns1.domain.com and ns2.domain.com
But my domain went down and I cannot ping it.
If I set up my DNS on my PC manually to ns1 it pings.
But without it it is not working.
On my DA I set up:
domain.com. NS ns1.domain.com.
domain.com. NS ns2.domain.com.
ns1.domain.com. A EX.TER.NAL.IP1
ns2.domain.com. A EX.TER.NAL.IP2

http://www.intodns.com shows (3-years) old IPs:

Domain NS records Nameserver records returned by the parent servers are:

ns1.domain.com. ['194.182.16.249'] [TTL=172800]
ns2.domain.com. ['194.182.16.250'] [TTL=172800]

a.gtld-servers.net was kind enough to give us that information.

What am I missing?
 
Last edited:
I set up two DirectSlave DNS ns1.domain.com and ns2.domain.com on different locations and connection is OK.
Something in your explanation seems missing.

DirectSlave are only slave servers, you should have one master server. If you use namings like ns1 and n2, then normally ns1 is your master server on you main DA machine.
Then DirectSlave is running on a slave server on a different location and you connect to it with DA Multiserversetup from the master (which is ns1 and is not a DirectSlave server).

So either you forgot to mention which is your master server (ns3?) or you have set up 2 Directslave servers without a master server which is not working either. Because a master server has to send the domains and updates to your Directslave server.
 
Back
Top