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

Question Why does named.conf hold on to domain zones after their removal?

Stuart De Usoz

New Pleskian
Plesk Onyx Version 17.5.3 Update #70 Centos 6
Please help me figure out how to properly reconfigure /etc/named.conf
I notice domain zones with domain names that were previously removed from Websites and Domains are still there and assuming this may pose a security risk I would like to see them removed.
However at top of config we have

#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
// $Id: named.conf,v 1.1.1.1 2001/10/15 07:44:36 kap Exp $
//

I ran

plesk repair dns,
service named restart

and everything is ok, but named.conf remains unchanged
 
What about

# plesk repair db

There may be orphaned dns records in Plesk database.
 
Hi Igor, thanks for you reply,
But that didn't help.. I just ran

plesk repair db
plesk repair dns
service named restart

and still find previously removed domain entries in /etc/named.conf file
 
No, should I install that?
No, I assumed that this extension could be the cause of the problem.
I'd suggest you contact Plesk Support Team for investigation and fixing this issue directly on your server.
 
Back
Top