Adding 3rd DA server and tertiary DNS

WholesaleDialup

WholesaleDialup

Verified User
Joined
Sep 25, 2004
Messages
178
Location
San Antonio, TX
I have been happily running most of my domains on 2 DA servers for a while with a third DA server hosting domains I just hadn't moved yet.

I finally have all the old domains moved to one of the two newer DA servers.

The 2 new DA servers each run slave DNS for the other. Works great, I add a new domain and slave records get created on the other server regardless of which server I create the domain on.

All DNS servers are listed exactly the same with the registrar ns1. and ns2. and all works perfectly.

Of course, now I gotta go messin' with it.. Ha ha..

Now that I have an extra DA license, I want to light up a third DA server to offload some of the domains to. I would also like to make this server primary DNS for all domains it host, with the other two servers as slave DNS.

On the other servers, I want to eventually change the registrar records and add the new DA server as Tertiary DNS. Of course before I do that, I will need to get the two existing DA servers to start writing out their records to the new DA server's DNS.

I get how DNS works in general but is there a guide or any advice on how best to do this cleanly with DA? I think I get it but before I start cracking into this, I figured I would ask all the smart people on the list for a little advice :-)

Thanks..
 
Hello,

Not too sure what your question is about. If you already use Multiserver feature on two DA servers, then there is nothing difficult to add the third one. You can use: ns1, ns2, ns3 with your servers.

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

If you have any specific questions, please feel free to ask them here.
 
zEitEr said:
Hello,

Not too sure what your question is about. If you already use Multiserver feature on two DA servers, then there is nothing difficult to add the third one. You can use: ns1, ns2, ns3 with your servers.

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

If you have any specific questions, please feel free to ask them here.
Click to expand...

Probably just over-thinking it. After further thought, it seems pretty clear now.

Just need to work through moving domains/users from one box to the other. I guess I need to uncheck the "Domain Check" and "User Check" when I make the moves. Not sure though if I need to delete the DNS on the DA servers that will be the slaves (since one will be the primary DNS at time of move) or if DA will just make the old primary DNS slave when I add the domain to the new DA server.
 
When using Multiserver function of Directadmin we have no Master/Slave DNS. The all server in a cluster are masters only.

If you going to move domains from one server on another within the cluster, then you can go 2 ways:

Noticeable downtime:
1. backup account/domains(s)
2. remove account/domain(s) on old server
3. restore account/domain(s) on a new server.

or

Less downtime:
1. Backup account/domains(s)
2. Disable Mutliserver function on new server
3. Restore account/domain(s) on a new server
4. Enable Multiserver function and update DNS

(later, in 24-48 hours)
5. Disable Multiserver function on old server
6. Remove account/domain(s) on old server
7. Enable Multiserver function on old server
8. Initiate DNS update from new server

I hope I did not miss anything.
 
zEitEr said:
When using Multiserver function of Directadmin we have no Master/Slave DNS. The all server in a cluster are masters only.

If you going to move domains from one server on another within the cluster, then you can go 2 ways:

Noticeable downtime:
1. backup account/domains(s)
2. remove account/domain(s) on old server
3. restore account/domain(s) on a new server.

or

Less downtime:
1. Backup account/domains(s)
2. Disable Mutliserver function on new server
3. Restore account/domain(s) on a new server
4. Enable Multiserver function and update DNS

(later, in 24-48 hours)
5. Disable Multiserver function on old server
6. Remove account/domain(s) on old server
7. Enable Multiserver function on old server
8. Initiate DNS update from new server

I hope I did not miss anything.
Click to expand...


The less downtime approach is what I have done in the past and was my plan this time more or less. I have done this before, just not with 3 servers setup in mutli-server DA mode.

Much of what I am looking for is just confirmation, re-assurance and updating my brain before moving forward again. You have been really helpful and I appreciate it.

The one thing I am a little puzzled about is that you say that all DA servers are Masters.. Hmm.. In my setup, the remote server acts as a slave. Example, if I update the DNS or Server A and Server A is where I have the domain setup, then it notifies server B. I don't think I can or should make changes to the same domain on server B. DA even shows that the data is not local on server B, it seems to know that it's a slave.

No?
 
Well, I guess in the traditional sense of "Master/Slave DNS" you are correct, they are both masters. What I am seeing in DA under the DNS manager is the indicator if the "data" is local or not. So all the domains that live on server A, show as Local Data=No on server B.

I guess I have always looked at this like a Master/Slave setup and have never changed the DNS On server B for a domain that has it's site and mail etc on Server A.

So, we are on the same page, I just wanted to clarify what you meant. Thanks again.
 
You must log in or register to reply here.
Back
Top