[Multi Server] Help with the new dns clustering system

X

XBL

Verified User
Joined
Nov 30, 2004
Messages
45
Location
Castricum, The Netherlands
Hi,

We just updated to the new DA version 1.25.0. This function includes the 'Multi Server'-function, one function we've all been waiting for (and hopefully being build further to support every service to be clustered).

But the function is documented yet, so I have no clue how it actually works. I don't have DA running on the box we want to use as secDNS, so I guess we need to do it trough Apache or something (like in the example screenshot in another topic on this new function).

But how does it work?

- I add the IP to the mutli server panel.
- Together with a user+pass: which user? A system user on the secondary server? The user bind is running on on the secondary server?
- I need some scripting on the secondary server, can some point me to what these scripts should do + how I get the primary server to execute these scripts?

If I miss some obvious info somewhere, I would appreciate a link. If it's not documented yet, I hope it will be fast. Otherwise, I hope someone knows the answers to my questions.

Thnx.

Jochem
 
I think that you will need 2 servers with DirectAdmin to have this working. Both setup with Multi Server turned on.

Server A has Server B in the list of external servers and the other way round. Both using an admin user to connect.

Pretty fair guess I think ;)
 
why don't i see anything for that clustering in my panel? DO i need a skin update?
 
@getUP: According to the explanation on the version page, you don't need DA on the secondary server. But I have no clue on how it should work, if you don't have DA on it...

sander815 said:
why don't i see anything for that clustering in my panel? DO i need a skin update?
Click to expand...
I use the enhanced skin with version 1.25.0. You do run the new version, right?

jochem
 
The idea is easy.

Server A;
Write a bash script fetching all your domains from named.conf and parse it into a text file. Make that accessable in any way, can be FTP or Apache, you name it. If you're doing it via Apache remember to add host restriction to who can download the file (only Server B and your company IP to verify how things go).

Server B;
Download the text file and parse it. Now you have a list of domains available running on the main server.
Then, use the API and store a raw save of the zone.
dns zone saving uses the CMD_API_DNS_ADMIN?action=rawsave&domain=domain.com command
Click to expand...

But hey, this is just the idea.
 
Or just use Master2Slave that Jeff Lasman posted. It will work with any bind-based servers.

Regards,
Onno Vrijburg
 
Chrysalis said:
if my slave server also has non DA domains will they continue to function?
Click to expand...

It seems that the new functionality checks bind (via DA) on the 2nd server to determine if the domain name exists and when it copies the zone it sets it up in bind and not in DA. DA will not remove any zones so your non-DA zones should be fine.

Regards,
Onno Vrijburg
 
You must log in or register to reply here.
Back
Top