• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

named/DNS randomly losing records

C

cmurphy@

Guest
over the past week since upgrading to plesk 7.5.3 (plesk did the upgrade), we have noticed ALOT of issues around the named service.

Specifically with domains zone files just all of a sudden not listed in the named.conf file.

while i know how to fix this problem, by:

a) editing the named.conf file to include the zone information for these domains

or

b) logging into plesk, selecting the domain which has all of a sudden stopped working, and then clicking "dns", disabling it, then re-enabling it.

Whats more important and what i really need to know is why the (*#$ this is happening to begin with. With domains randomly it seems, stopping to work, this looks very bad for us. down time is nuts !!!

there is no order, or pattern to the issue, half of one customers domains will work while all of anothers will be fine...

I know that psa writes the zone information to the psa database, and uses that to write the named.conf file.

So basically, how do i get PLESK to recreate the entire named.conf file from the database, and secondly, why are the entries in the psa database all of a sudden, randomly missing certain domains?
 
Back
Top