• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Manuel upgrade to Debian 13 - BIND stopped working

the story continue.....

the named.conf is still deleted, but now bind9 states that entries in the non-existing file still not match the dnssec-policy

/etc/named.conf:113: zone 'DOMAIN': option 'dnssec-policy DOMAIN' has no matching dnssec-policy config
/etc/named.conf:125: zone 'DOMAIN': option 'dnssec-policy DOMAIN' has no matching dnssec-policy config

but raw 113 and 125 in that file don´t exist.. the whole file don´t exist.. so where does bind9 take that infos from?!
 
You must log in or register to reply here.

Similar threads

S
Question Error to update 18.0.73.2 - Apache2 error in line 2 in /etc/apache2/conf-enabled/php_cgi_wrapper.conf
Replies
2
Views
454
sistemas@chequemotiva
S
K
Issue Planified Task not working anymore after upgrading Debian/updating Plesk
Replies
9
Views
1K
Kouenteen
K
q-quan
Resolved Can't run Plesk Premium Antivirus (drweb)
Replies
5
Views
550
Sebahat.hadzhi
Sebahat.hadzhi
R
Resolved Mariadb stop working in upgrade from Ubuntu 20.04 to 22.04
Replies
1
Views
2K
rodrom
R
@
Issue Plesk Task Manager Issue not starting
Replies
12
Views
4K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top