problem transfer account with multi server setup

R

remikk

Verified User
Joined
Apr 30, 2008
Messages
158
Location
Poland
HI

I have two servers - da1 and da3 which use multi server setup.
I've read http://help.directadmin.com/item.php?id=97 that I have to uncheck "Domain check" to transfer account from one to second server.
I understand that if I did that, I can backup account from da1 and restore on da3. But when I restore I have error "domain already exist". So something doesn't work.
 
I just did a account transfer with a multi server setup.

If you have a "domain already exist", delete the domain from the server it's not local on and so not really used on.
After that, transfer the account with the domain and you should be fine.

However, normally unchecking the Domain check should be working. But I always check manually just to be sure.
 
Last edited:
If I delete domain on da3 then on source server da1 domain also is deleted. I think it not should be happend.
What if some account has 100 domains ? I'm not sure that I should delete domain.
Code: 
 When you disable the "Domain Check" and leave Zone Transfer enabled, DA will blindly add the domain to the exernal machine (it still checks locally of course), and will overwrite any zone information that might already be there
 
Did you wait about 1 minute?, have you disabled multi-server setup before delete the zone?

Actually, if you need to move a user the steps should be:

backup on da1
move on da3
delete user on da1
restore on da3

Otherwise, if you, for security reason wanna be sure restore complete on da3 before delete on da1, you should disable multi-server on da3 and remove the dns zone on da3, or, manual edit named.conf and comment/remove the related line (just disabling domain check).

Hope i've been enough clear.

Regards
 
SeLLeRoNe said:
Did you wait about 1 minute?, have you disabled multi-server setup before delete the zone?

Actually, if you need to move a user the steps should be:

backup on da1
move on da3
delete user on da1
restore on da3

Otherwise, if you, for security reason wanna be sure restore complete on da3 before delete on da1, you should disable multi-server on da3 and remove the dns zone on da3, or, manual edit named.conf and comment/remove the related line (just disabling domain check).
Click to expand...

So, I tried use the same steps like with no multi server setups.
change TTL
change IP for account
disable IP from shell by ifconfig down
restore on da3
setup the same IP on da3
put account to the same IP like on old server.
then delete account on the da1.
I know that this method work perfectly without multi server setups.

So, if I have to disable multi server setup and delete zone manually it is complicated with account which have 100 domains.
Following help:
"When you disable the "Domain Check" and leave Zone Transfer enabled, DA will blindly add the domain to the exernal machine (it still checks locally of course), and will overwrite any zone information that might already be there"
This is not helpful and should be changed because DA will not blindly add the domain.
 
That's normal, DA will not check remote server, but, if da3 is also a remote server for another server (ok sound werdy but i dunno how explain better) da3 will have a local zone for the same domain...

In the DNS zones you will have the same domain set as "not local" and when you will try to restore the domain that will make it fail.

Actually, to me, it seems the best way to do that for dont risk to overwrite (unless you manually wanna do that) already existing dns zones.

For the 100 domains you have, i would suggest to disable multi server, delete all the "not local" zones, restore accounts.

Then you will manually need to make the syncs i suppose via ssh, it depend if da1 server will be shut down or not and how you wanna setup your dns servers.

Regards
 
I understand now what have I do.
But check domain option is not working as it should according to the documentation.
If disable check domain but leaves the multi server enabled, then according to what is written in the documentation I should be able to override the domain. Unfortunately it is not.
I have to turn off multi-server and delete domain. If I leave multi-server enable and try to delete "not local" domain on da3 then she is deleted from da1 also.
I try to understand what is intended in this case the option "check domain" if I can not use it.
 
Have you tried this:

Turn Multi Server Option off completely for all domains, do the transfer, and then turn it back on for all domains.

Jeff
 
Im not sure this would work Jeff.

Cause, if you disable it, the already trasnfered domain on your server ( i mean the zone listed as "not local" ) would already be on server and import will fail for "domain already exist"

Am i wrong?

Regards
 
I guess the issue is what the OP means by transfer account. I'm presuming (perhaps incorrectly; I didn't reread the entire thread carefully) OP means using the Admin Backup/Transfer, which for me always works if the site already exists but Multi User is turned off; of course it will install it at the same IP# where it's already set in the local DNS, but that's easy enough to change afterwards.

Jeff
 
I see, maybe you're right, usually i remove from remote server before import on a new server :)

PS. Let me know about nagios/munin ;)

Regards
 
Cause, if you disable it, the already trasnfered domain on your server ( i mean the zone listed as "not local" ) would already be on server and import will fail for "domain already exist"
Click to expand...
I think Jeff is right.
I transfered a couple of servers until now and never had this problem.
When one server is multiserver for another, I disable multiserver setup on both servers.
Then I disable the domain check as stated in the directadmin help.
Then I do the transfer. There will be no complaints about existing domains, they will just be overwritten.
Enable multiserver setup again (*)

(*) I move also the multi server setup to another server. Because I transferred all accounts from server to server, not just a couple.
However, it might go wrong when just a portion of the domains are moved. Because the previous local ones, will become remote was, they should not exist as local ones on the old server anymore. I don't know exactly how this can be fixed easily, except for deleting the accounts on the old server before activating multiserver setup again.
 
I've tested a two option to transfer accounts.

1) On both servers da1 and da3 I had multi-server on before I started transfer
First I've turned off multi-server on both servers. Stop IP (ifconfig eth0:4 down), backup user1 on da1 and after try to restore on da3. Off course I had domain already exist because she is as non-local domain on da3. So only what I need I have to delete non-local domain and then restore again. Then I can use normal steps which I used, so add IP to da3 and change IP for user (the same like was on da1). After that check is that everything working correctly and delete account on da1. Turn on multi-server. Multi-server synchronize domains only if I did some changes, so I need to do it. On da1 domain will non-local, on da3 local domain.
2) Only da3 has multi-server on. da1 is master nameserver.
Turn off multi-server on da3. Restore user account, change IP, check that everything working OK and then I can delete account da1.

So I understand that I need to turn off multi-server and first option work correctly but non-local domain from destination server should be deleted manually.
But I think documentation should be changed because there is only about disable "domain check" not turn off multi-server, non-local domain should be deleted manually and after turn on multi server I need some fake change with account to force transfer domain via multi-server.
 
You must log in or register to reply here.
Back
Top