superfun2k23
New Pleskian
- Server operating system version
- Debian 13
- Plesk version and microupdate number
- 18.0.74 #1
Hi, I have DNSSEC problems with Debian 13.
Already the problems started with upgrading 12.12 to 18.0.74 manual, but then support told me, manual upgrading is not supported, so I installed fresh Debian 13 and it still not works.
Every Domain with activated DNSSEC gets errors and keeps bind from starting..
It states that no matching dnssec-policy ist found for the domain used..
The problems started with upgrading to debian 18.0.74 and Debian 13, so it seems to be related to bind9 version used in Debian 13/Plesk 18.0.74, because in 73/deb12 IT used old auto-dnssec and moved now to new dnssec-policy and yet this ist not working..
Deleting named.conf ist a workaround, bit the file gets recreated by plesk, so bind stops working from time to time.
So maybe someone from support can look at this Situation?
My license isnfrom reseller, so any contact to support would take Long time, since my reseller first have to check and verify.. I hope to get a solution here fast
Already the problems started with upgrading 12.12 to 18.0.74 manual, but then support told me, manual upgrading is not supported, so I installed fresh Debian 13 and it still not works.
Every Domain with activated DNSSEC gets errors and keeps bind from starting..
It states that no matching dnssec-policy ist found for the domain used..
The problems started with upgrading to debian 18.0.74 and Debian 13, so it seems to be related to bind9 version used in Debian 13/Plesk 18.0.74, because in 73/deb12 IT used old auto-dnssec and moved now to new dnssec-policy and yet this ist not working..
Deleting named.conf ist a workaround, bit the file gets recreated by plesk, so bind stops working from time to time.
So maybe someone from support can look at this Situation?
My license isnfrom reseller, so any contact to support would take Long time, since my reseller first have to check and verify.. I hope to get a solution here fast