DirectAdmin and Mysql as Bind Repo

[tincboy]

I want to build an infrastructure that centralize DNS for all of our hosting servers, So we can move a website from a server to another without need to change name servers,
Also I want to replicate the central DNS server to 2 or 3 more servers to increase up time,
So I believe that this complex scenario may require to store zones' data into database,

Does DirectAdmin allow us to store data into DB?
If so do you guys have any advice or suggestion about using which kind of packages or configuration?

Any help will be much appreciated.

 

[SeLLeRoNe]

actually you should just use 1/2/3 server with master2slave replicator and set all directadmin server to send dns zones over there (also useable for non-da server i suppose with some adjust).

Why is mysql necessary? And forgive me maybe ive missunderstood, but, nameserver is already centralized if you use for example ns1.domain.com ns2.domain.com ns3.domain.com for all your domain... just those 3 (can be more or 2) will reply for dns request, so, unless you made customized ns for each domain, you already can have it easly... and.. i dont see a reason for use mysql...

Regards

 

[tincboy]

Does this utility that you've suggest support propagation of updates from slave to master and also from master to slave?
What about confilicts that may occur between master/slave zone files?

 

[SeLLeRoNe]

What do you mean for update slave to masters? All server would be slave and the e main ns will be the masters.

Actually not, if a server have domainA.com and you add domainA.com from another server he will not recognize is already there... thats a limit.

But, if you are using all directadmin server you should consider the Multi-Server functionality that can make your server know of any domain in this way:

server A <=> server B

So, if in serverA you add domainA than you cant add domainA on serverB

Regards

 

[tincboy]

I mean if a client create a subdomain for one of his domains, and this cause the zone file to be edited?
Does it make the related zone file on master to be updated?

 

[mr.applesauce]

Any time a change is made the serial is updated and it knows to send it to slaves.

 

[tincboy]

what about change in slave? does it cause the master to be updated?

 

[mr.applesauce]

You cannot make dns changes on a slave...They need to be made on the master only.

 

[tincboy]

You cannot make dns changes on a slave...They need to be made on the master only.

this is not good, because the clients may create a new subdomain any minute

 

[mr.applesauce]

This is how dns works. You can use the directadmin api to make dns changes.

 

[tincboy]

This is how dns works. You can use the directadmin api to make dns changes.

I belive a true replication senario must support both side changes in zone files,
Are you sure this utility just replacate changes which are made in master?

 

[nobaloney]

Nope; you're wrong. Slaves always get their updates from masters; it's a limitation of the definitons of DNS service.

If you want DNS on your DirectAdmin hosting server #1 to also be available on your DirectAdmin hosting server #2, that's not a master/slave scenario. That's a duplicate master scenario, with code built into DirectAdmin doing the managing. In that case, any user can change his own DNS and it will appear on the other DNS servers you've set up in your DNS cluster.

In a true Master/Slave scenario, the DirectAdmin servers become hidden masters, so each user can change his own DNS anytime he wants and it will work it's way out to your slaves, which are the systems you publish as your DNS servers.

There are two ways to do this: one is using Master2Slave DNS Replicator (which I paid to have written and licensed as open source software). The limitation is it takes up to thirty minutes for the slaves to be updated. That's generally not a problem because most people expect DNS to take time to update.

If it is a problem for you then use the other method built into newest versions of BIND; search these forums as someone wrote about it here once:

There's now something built into BIND which notifes the slave server to create a new zone record in the named.conf file, so you can create new zones only on the hidden master and have them picked up on the slave servers. I have no experience with it and don't know how well it works.

While the RFCs (and BIND) allow you to mix master and slave zones on the same server, if you're going to do it on a DirectAdmin powered server you'll need to make sure your zone files are kept in the slaves subdirectory or DirectAdmin may have problems.

The only method I support at no charge is Master2Slave DNS Replicator, and then only if you've had it installed through our commercial NoBaloney installation service.

But the others work as well.

Jeff

 

[nobaloney]

I didn't answer your question about managing DNS through MySQL in the above email.

BIND doesn't work with MySQL; it works with flat files. There are other DNS systems which do, but when we tested them MySQL replication always fell apart within a few hours, so instead we had Master2Slave DNS Replicator built.

Even if you get it working you'll still need software to scrape the zone files which DirectAdmin builds, and convert them to a MySQL database.

Jeff