• 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.

Resolved DNS Zones present even if disabld in Plesk

H9k

Regular Pleskian
Hi there!
I found myself having some DNS zone active in the DNS server, even though DNS is disabled for those domains in Plesk.
Running 'plesk repair dns' did not fix the problem, but enabling and disabling DNS in Plesk did get rid of those zones.
Now my question is: how can I get a list of all the domains that have DNS disabled, so I can check if they are also affected?
 
Ok apparently I found the cause of the problem. I had migrated some domains some months ago, and in the migration file I had DNS deactivated for the main domain and dns set to false for its aliases, but for some reason while the main domain did not get the zone and the aliases had the DNS syncrhonization feature disabled, the aliases actually got zones.
By looking at my old migration file I can see that only two domains were affected in my case, so I fixed the problem, no need for support here :)
 
Back
Top