Second nameserver

S

splatz

Verified User
Joined
Nov 20, 2010
Messages
6
Hi everyone,

We use the multi-server option of DirectAdmin to transfer all zones of all servers to server 1 on which nameserver 1 and nameserver 2 are set up. Now because we have servers across 2 datacenters we want to have the second nameserver in another datacenter then nameserver 1. But, how do I set up a nameserver in DirectAdmin for a domain which isn't hosted on that server?
 
Not sure, I've understood you correctly. Could you explain more detailed?

If you want to add a zone into DNS manually, use "DNS Admin" on Admin Level.

If you want to transfer all zones to the server located in the 2 datacenter, turn on "multi-server option" on both of them and run in SSH (on the 1st server):

Code: 
echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue

It'll make directadmin to update and transfer all DNS zones.
 
252188

Thx for the reply but it's not quite what I mean. I'll try to explain better;)
You can set up 2 nameservers in directadmin using Nameservers under Reseller level, but that isn't possible if the domain isn't hosted on the server. So how to create for instance ns2.google.com when google.com isn't hosted on the server?
 
If you want to move one NS from the first server to the second one. You don't really need to use Nameservers under Reseller level at all (you can remove them from there, I believe). Change IP for the ns2 at your registrar and in DNS zone. That should be enough.

I hope, I didn't miss anything, while I do not use "Nameservers under Reseller level" anymore.
 
splatz said:
Thx for the reply but it's not quite what I mean. I'll try to explain better;)
You can set up 2 nameservers in directadmin using Nameservers under Reseller level, but that isn't possible if the domain isn't hosted on the server. So how to create for instance ns2.google.com when google.com isn't hosted on the server?
Click to expand...
The only reason for setting up a nameserver under a reseller is so it will be automatically assigned to new domains as they are set up on the server. To avoid using IP#s of your own server simply set them up as virtual domains.

I haven't done this in quite a while; I may not be as clear as I should be; I may have mis-remembered something, but as I recall this is what I've done in the past.

I also remember posting on this issue years ago.

Jeff
 
Sure, if we say about "Set the Nameservers that will be assigned to new users":

Nameserver 1
Nameserver 2

There should be both nameservers set.


But I previously spoke about assigning "With 2 Selected IP's" (virtual) nameserves.
 
You don't select nameservers with IP# if they're not on your server.

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