• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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
Issue BIND on Debian 13 / 18.0.74 problems with DNSSEC??
Replies
3
Views
1K
scsa20
scsa20
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
1K
sistemas@chequemotiva
S
UnS3eN
Issue httpd won't start
Replies
9
Views
2K
pleskpanel
P
K
Issue Planified Task not working anymore after upgrading Debian/updating Plesk
Replies
9
Views
3K
Kouenteen
K
q-quan
Resolved Can't run Plesk Premium Antivirus (drweb)
Replies
5
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top