DNS and stopping multiserver setup

D

DionWales

Verified User
Joined
Mar 9, 2011
Messages
14
Hello,

I remember I had some issues a few years ago, so I would like to ask the community how to get this done without issues.

I have three server:

- PowerDNS server which is my ns2
- DirectAdmin server for shared hosting which has PowerDNS as ns1
- DirectAdmin server for one specific client, which has multiserver enabled to do zone transfers and domain check to ns1

We now want to decommission the DirectAdmin server that is used for one client, but: the DNS zones must be kept, because the domains are still be used. So I want to disable the Multi Server option on that server, but if I remember correctly, years ago the DNS zones on the other DirectAdmin server would be removed after that.

So:

How can I disable the multi server setup and keep the DNS zones on the "DirectAdmin server for shared hosting that is acting as ns1"? And beside that I need to attach all those domains to an account, so the client can manage his DNS zones.

Help will be appreciated.
 
DionWales said:
but if I remember correctly, years ago the DNS zones on the other DirectAdmin server would be removed after that.
Click to expand...
No nothing is removed unless you do that yourself. If you just disable the multi server setup, then no DNS updates to the remote server (which is setup in multiserver setup) is done anymore, but the records will be kept.

So disabling multi server setup will only disable the connection, nothing else. DNS zones in DA are kept.

However, if the DA server is used as a "slave" dns server then it will see the dns data as non local data.
So if you want to use them on the DA server so the user can manage the DNS zones, indeed an account must be created with all domains. However either DNS records get overwritten or you get an error they already exist.

So I don't know how to solve that part.
 
Hello,

If you want to create/import domains which already exist in DNS on the server, then you will need:

1. backup DNS zones, e.g.:

Bash: 
cp -rpv $(da config-get nameddir) /root/DNS.backup

3. remove DNS zones (which you will re-create/re-import later)

4. create/import accounts

5. restore DNS zones and update zone serial numbers whenever its required

DionWales said:
And beside that I need to attach all those domains to an account, so the client can manage his DNS zones.
Click to expand...
 
Richard G said:
No nothing is removed unless you do that yourself. If you just disable the multi server setup, then no DNS updates to the remote server (which is setup in multiserver setup) is done anymore, but the records will be kept.

So disabling multi server setup will only disable the connection, nothing else. DNS zones in DA are kept.

However, if the DA server is used as a "slave" dns server then it will see the dns data as non local data.
So if you want to use them on the DA server so the user can manage the DNS zones, indeed an account must be created with all domains. However either DNS records get overwritten or you get an error they already exist.

So I don't know how to solve that part.
Click to expand...

Good to hear that "breaking" the multiserver setup is not giving issues.

zEitEr said:
Hello,

If you want to create/import domains which already exist in DNS on the server, then you will need:

1. backup DNS zones, e.g.:

Bash: 
cp -rpv $(da config-get nameddir) /root/DNS.backup

3. remove DNS zones (which you will re-create/re-import later)

4. create/import accounts

5. restore DNS zones and update zone serial numbers whenever its required
Click to expand...

Thank you. To make it more clear: no accounts will be moved. The client servers will be removed and the sites on this server are hosted now somewhere else. Only the DNS would be used, so therefore I need to attach them to a "dummy" account for them on the shared / ns1 server so they can change records and stuff.
 
You must log in or register to reply here.
Back
Top