cPanel & WHM Version 80 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!
 

MySQL Backend for PowerDNS

benny@cpanel.net shared this idea 2 years ago
Open Discussion

As a webhosting provider and server administrator I would like cPanel to switch the PowerDNS nameserver integration to MySQL rather than bind files to help me integrate with other PowerDNS clusters more easily.

Comments (9)

photo
1

Would be nice to have full featured PowerDNS with mysql backend supported at cPanel.

photo
1

Would love to have this as well. One of the most benefit of using PowerDNS is Master/Master replication which utilize the well-proven MySQL replication

photo
2

PowerDNS is meant to be used in a SQL-based backend. Running flat files is the same as running bind, which disregards all of the features of PowerDNS. PowerDNS is going to have a hard time scaling to 100,000 zones, if it's not backed by a SQL-based backend.

photo
1

I'm curious as to why cPanel opted to go for the normal zone file backend instead of using MySQL out of the gate. I have a sneaking suspicion it may be because of the development time required to setup slaves / masters within cPanel DNS so they opted for a this simpler solution which they could re-use their existing stuff (dnsadmin / etc).


It really offers no flexibility and isn't ideal. The MySQL backend should be supported out of the gate.

photo
1

In this case, there were two primary motivations for shipping without MySQL support. The first was, as you suggested, the lower development requirements which allowed us to ship PowerDNS support more quickly.


The second was actually more about how people use our software. Less than 5% of cPanel & WHM servers host a large number of domains. So, while there are other reasons to use MySQL as the backend, we wanted to see if the amount of work required would actually benefit a large enough portion of our user base to make it worthwhile.

photo
2

They don't need to setup MySQL replication. Most users are just going to setup each DNS server, as a DNSONLY machine and it will act as a stand alone server. The more advanced users that want SQL replication and not the overhead of DNSONLY on their DNS servers, can set it up themselves.


The functionality of pdns, compared to mydns is very similar. You should be able to use a lot of the same codebase to get it to work with pdns, the only differences is the table name(s) and order of fields for the most part.


Would be happy to assist in any way to get this functionality added.

photo
photo
1

Many ( if not most ) cPanel deployment are through billing software, which also provide domain registration.

And one of the most common issue I've had so far from the customer side is they're having questions "Where should I manage my DNS records? On the registrar panel, or through the webhosting panel?"

1. For beginners, usually they will go with the webhosting panel

2. For most advance user, most of them will go through the registrar panel

And the other issue is for companies hiring web developers, they want to give flexible way to the developers for modifying DNS records as needed, but would not give access to the registrar panel

All those issues leads to dual DNS management system, which should be resolved if cPanel have the ability to have Authoritative DNS servers with MySQL backend, where people will have the flexibility to manage the zone, from their preferred panel as needed, and can go back and forth between both domain registrar panel and webhosting panel

photo
1

We would absolutely love if we could have PowerDNS with a MySQL back end. It would be even better if we could convert/migrate our BIND based DNS only cluster over to PowerDNS/MySQL.

photo
1

Having a mysql backend will make it easy to integrate to other services