MySQL Backend for PowerDNS
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.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Would be nice to have full featured PowerDNS with mysql backend supported at cPanel.
Would be nice to have full featured PowerDNS with mysql backend supported at cPanel.
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
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
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.
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.
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.
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.
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
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
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.
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.
Having a mysql backend will make it easy to integrate to other services
Having a mysql backend will make it easy to integrate to other services
Would be great to combine with this DNSSEC
Would be great to combine with this DNSSEC
Hoping this is added soon, I've spent days trying to get this to work properly. I switched to PowerDNS from Bind in WHM and followed all the directions due to the memory benefits. However the recommendations on many sites are to use the generic Mysql backend, which WHM doesn't configure, although it doesn't tell you, so it's half set up and doesn't work properly. I realised I had to unset the cPanel version and install a newer version via Yum. The cPanel version is outdated and it looks like newer versions included security fixes.
Having manually set up a powerdns database and MySQL user, all looks good but it still doesn't utilise the database. Using the guide at the site I was able to insert test entries, example.com etc. I can use Dig and Netstat shows it is listening on port 53. The /etc/powerdns/pdns.log never gets updated, I've checked ownership and permissions. It's difficult to tell what's up as there are no obvious errors showing when checking systemctl status pdns, so I'm now stuck in limbo. The forum advice inevitably is to open tickets but this is no use to end users because the CPanel licence is provided by a webhost is company, so you can't.
Please could you implement an automated process to switch to the latest version of PowerDNS with MySql backend support, and options to turn on the web server API without having to manually edit conf files so that it can be used with 3rd party monitoring services like Netdata? This would save a lot of hassle and frustration, and concern about causing potential issues by switching from Bind.
Many thanks.
Hoping this is added soon, I've spent days trying to get this to work properly. I switched to PowerDNS from Bind in WHM and followed all the directions due to the memory benefits. However the recommendations on many sites are to use the generic Mysql backend, which WHM doesn't configure, although it doesn't tell you, so it's half set up and doesn't work properly. I realised I had to unset the cPanel version and install a newer version via Yum. The cPanel version is outdated and it looks like newer versions included security fixes.
Having manually set up a powerdns database and MySQL user, all looks good but it still doesn't utilise the database. Using the guide at the site I was able to insert test entries, example.com etc. I can use Dig and Netstat shows it is listening on port 53. The /etc/powerdns/pdns.log never gets updated, I've checked ownership and permissions. It's difficult to tell what's up as there are no obvious errors showing when checking systemctl status pdns, so I'm now stuck in limbo. The forum advice inevitably is to open tickets but this is no use to end users because the CPanel licence is provided by a webhost is company, so you can't.
Please could you implement an automated process to switch to the latest version of PowerDNS with MySql backend support, and options to turn on the web server API without having to manually edit conf files so that it can be used with 3rd party monitoring services like Netdata? This would save a lot of hassle and frustration, and concern about causing potential issues by switching from Bind.
Many thanks.
With mysql support it would be easy to setup a mysql cluster and have a simple second nameserver without having to go through installing a cpanel dnsonly server.
With mysql support it would be easy to setup a mysql cluster and have a simple second nameserver without having to go through installing a cpanel dnsonly server.
Replies have been locked on this page!