Moving website between two directadmin servers that are sharing zones?

Magistar

Verified User
Joined
May 31, 2014
Messages
105
Hi there I am unsure how to proceed here.

Normally I test my website by transferring the reseller backup to another directadmin install. Then I import it there using local ip. I change system32/hosts on my private pc so that I can only I visit this server so I can safely test website changes.

I have recently changed to using my own directadmin servers with multiserver zone sharing (ns1 and ns2). Now I am afraid that when I import the same website on the second server that the nameserver info will update and that therefore I cannot properly test my website.

How do I proceed here?

edit:
I tried it. The backup did import but there is no associated domain. Therefore it resolves as "Apache is functioning normally". How can I add the domain without the nameservers updating (they DA installs are connected). I checked the multiserver settings and "Domain Check" was not checked.

What I want is the domain to resolve on both servers without the A-records reflecting this.
 
Last edited:
I always temporarily disable the multiserver setup.
After everything is working fine, I enable it again and then run the datatasq.queue to have domains transferred to ns2 (or ns1) from the new server with the new ip.
This way the nameserver at first instance is only update locally when testing and not in the real ns1 and ns2.

If al is well, it change the nameserver ip's at the registrar and enable multiserver setup again.
 
Sounds like a solid suggestion! Thanks.

To be sure I understood it correctly: So when I disable to multiserver both nameservers keep working because the information that was transferred "in" remains in the nameserver. And because it is disabled I can now temporarily add the domain on the other server?
 
You're welcome.
Yes if you disable multiserver, both nameservers keep working, only if a new domain is created or a change is made, that's only done locally and not transferred to the other server.
So you can indeed temporarily add the domain on the other server.

Just take care when you run the datatasq.queue afterwards. After enabling multi server setup, do this on the new server first, so the new ip's will get transferred the the older nameserver which is not replaced.
If you do it the other way around, it will result in your new server having the domains with the old ip's again. :)

So in fact when moving ns2 to a new server it would be like this:
1.) Disable multi server setup on both servers.
2.) Move domains from ns2 to new server and check if everything is ok.
3.) Enable multi server setup again.
4.) Run the datatasq.queue from the new ns2 so the older ns1 will get domains overwritten with the new ip's from the new ns2.
5.) Run the datatasq.queue on ns1, so ns2 will also get the domains from ns1 in the nameserver.
 
Back
Top