• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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