1 ip per server, Multi Server Setup

S

sokolkapl

Verified User
Joined
Mar 12, 2010
Messages
40
Hi,

I have 2 separate DirectAdmin installations.

server 1: domain1.com with hostname server.domain1.com, 1 IP 1.1.1.1
server 2: domain2.com with hostname server.domain2.com, 1 IP 2.2.2.2

Given I only have one IP per server, could I set up nameservers for ns1.domain1.com (1.1.1.1) and ns2.domain1.com (2.2.2.2)?

I know how to register my ns1 and ns2 with my domain registrar.

How would I go about doing it with DirectAdmin?
 
The mutli-server setup in DA already caters for the DNS to automatically populate from one server to the next.

The two IP's would be sufficient (barely) - you may want more (especially if you want SSL certificates etc).

To setup ns1, ns2 etc on your domain, you just need to create the appropriate A-Record (Address) in your DNS server:

Code: 
ns1      <ip address 1>
ns2      <ip address 2>

If your domain is pointed and managed on your DA box - it's as simple as doing this through the DA interface.

Then you just need to tell your Domain Registrar the info in the delegation part.

More info on multi-server (clusters) can be found here:

http://help.directadmin.com/item.php?id=97

More info on DNS aspects of the DA Control Panel can be found here:

http://www.site-helper.com/dns.html
 
Let me know if I got it right:

All I need to do is enable Multi Server Setup, add remote DirectAdmins in each server in Multi Server Setup menu, register ns1 and ns2 with my registrar, then add:

ns1 A 1.1.1.1
ns2 A 2.2.2.2

in DNS Administration for domain1.com, and I'm all set?
 
pretty much!

a quote from the KB article (link in my reply above):

So, if you have server A and add the IP for server B to the list, whenever you add a domain on server A, server B will receive a copy of the dns zone. Server B will now also be able to resolve the domain. Since this uses the API, nothing is needed to be setup with regards to clustering on server B to get data from server A transfered over to server B.

A sample nameserver setup would be (you can add more/change them as you need):
ns1.domain.com -> resolve to an IP on server A
ns2.domain.com -> resolve to an IP on server B
Click to expand...
 
Don't forget to create a records for the ns1 and ns2, in their domain zone files.

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