Server 2 on DA

S

shadowq

Verified User
Joined
Dec 5, 2010
Messages
97
Hello,

I've currently got a server with plesk (kjhosting.com), with NS's as ns1.kjhosting.com and ns2.kjhosting.com. I have now got a DA server, and want to have the DA server at s2.kjhosting.com, with NS's at ns3.kjhosting.com and ns4.kjhosting.com.

So what I've done so far-
I've set up A records on my plesk server for s2/ns3/ns4.kjhosting.com to point to my new DA main IP.
I've registered NS3 and NS4 and my domain registrar, where kjhosting.com is registered, and pointed them to the correct IP's.
I've put s2.kjhosting.com in my DA panel as server's hostname, with NS1 and NS2 as ns3/ns4.kjhosting.com.
I've added NS records on my plesk server for s2.kjhosting.com to be ns3/ns4.kjhosting.com (Is this one necessary? Without this step, intodns.com fails).

Now my problem- when going to http://www.intodns.com/s2.kjhosting.com, I see a whole bunch of errors (name servers didn't respond, can't find name servers, etc).
And when I goto http://www.opendns.com/support/cache/ to check if s2.kjhosting.com is resolving correctly, it claims that s2.kjhosting.com is now in the DNS.

Any help would be appreciated!

Thanks :)
 
If I nslookup ns2.kjhosting.com from either my plesk server, or my DA server, they both return NXDOMAIN.

Why?! I have the A record in plesk pointing to my DA server, and I have my DA server's hostname as s2.kjhosting.com. Isn't this all that DA needs?
 
It's got nothing to do with what DirectAdmin needs, but rather with what DNS needs, so I've moved your thread to the DNS subforum.

It appears your Plesk server has NS records inside your kjhosting.com zone file, to point requests for s2.kjhosting.com to ns3 and ns4 (your DirectAdmin server). So even with an A record in your Plesk server zone file, it won't get read; DNS will immediately look at your DirectAdmin server.

But your DirectAdmin server doesn't have A records for s2.kjhosting.com.

I'd suggest leaving a zone file in your DirectAdmin server (to keep you from accidentally ever setting up a domain name s2.kjhosting.com on that server), but to keep all necessary records for s2.kjhosting.com in the zone file for kjhosting.com on the Plesk server. Except those NS records for s2.kjhosting.com in your Plesk zone file. If you're using my scenario, then get rid of them; you don't want to point to the zone file on your DirectAdmin server.

Once you've done this, and your changes have propagated (give them 24 hours based on the TTL in your zones), look at intoDNS again.

You'll definitely find errors because you don't have redundant DNS; you may have others. We'll help you in this thread with the others. To fix the errors concerning not hasving redundant DNS you'll probably want to use one of your servers for NS1 and the other for NS2, and learn how to do slave DNS. There are some threads in these forums; the best way (in my opinion) is to use the Master2Slave DNS Replicator I had written for me. It's available (open source) on these forums but it requires some experience to get it to work with the different format Plesk uses for zone files. If you decide you'd like it and can't install it yourself, contact me if you'd like; I offer the setup as a commercial service.

Jeff
 
I've got rid of the NS records I had for s2.kjhosting.com in Plesk, and it seems to be working fine now, and resolving in openDNS's caches too.

However, intoDNS says that it doesn't check subdomains now (the same thing it says with another domain I have hosted at my Plesk server (ywam.asia) with elearning.ywam.asia hosted at my DA server).

Is this normal?
 
If you've got a main domain on one server and a subdomain (which is different from a servername) then the subdomain needs one or more ns records in the main zone file for the domain, pointing to the server DirectAdmin will create when you create the subdomain as a main domain on the DirectAdmin server.

Jeff
 
You must log in or register to reply here.
Back
Top