• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PowerDNS as Secondary DNS

MarkM

Golden Pleskian
Plesk Guru
Hello,

I am looking to use PowerDNS as secondary DNS by adding a Plesk server as a Supermaster. The Supermaster should allow the provisioning of new domains automatically BUT how does it react when suspending a domain? When a domain is suspended in Plesk, I would like for the PowerDNS slave to not respond as well.

Feedback and suggestions anyone?

Thanks!
 
Had a chance to test it, and it does not appear to suspend the secondary DNS.

Is there a way to accomplish this?
 
There are actually some benefits to retaining the DNS records. Specifically, it allows you to set up a default page that says something like "This site is suspended - contact support".

We use 4PSA's DNS Manager for DNS. A script running on the Plesk server created a file containing all dns records which the DNS Manager server then retrieves. Suspended domains don't appear in the list.

A setting in DNS Manager then allows you to decide what to do with domains that are no longer in the list - keep serving the records previously stored, or delete the records.

There are other ways to set it up too.

I'm sure you can actually create something similar yourself without too much bother. All you need is a really cheap VPS or two to act as the DNS servers.
1) Write a little script that dumps DNS records from the Plesk database (or maybe just copy from named's config?) and write them to a file
2) Write another little script that grabs that file, processed it and creates or updates the necessary records on the VPS.

(I'm sure there are complications I've not thought of, but that's the basics really).

Actually, I wonder whether you could just rsync the directory structure, at least for the master DNS server?
Hmm...

I'll bet someone's already done this one way or the other.
 
Back
Top