Issue Manuel upgrade to Debian 13 - BIND stopped working

[superfun2k23]

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?!

 

[nMLxTMJTZ]

Also for me with debian 13 not work, i set policy default but after DNS stop working and domain name not solved, have you a patch?

 

[superfun2k23]

I just reinstalled the whole server with Debian 12 and stay with for now.
Migration ist still not supported, so I don't risk my setup again.
When you have backup from Debian 12 install, roll it back

 

[Hangover2]

I only recommend major OS or database upgrades when a system is nearing end of life. Hosting requires 3 things: stability, stability, stability and I would not upgrade a customer’s running production server to Debian 13 in 2026 without a compelling reason. Debian 12 is still supported, and Debian 11 even has long-term support until August 31, 2026. Specific client requirements can usually be handled with Docker containers in Plesk.

I do not understand the constant push to adopt the latest operating system right away. The result is often instability, avoidable issues, and unnecessary service interruptions.

 

[nMLxTMJTZ]

any news from plesk?

 

[Hangover2]

31st of March 2026: How to perform dist-upgrade procedure on Linux server with Plesk?

 

[nMLxTMJTZ]

ok but i have a new installation of debian 13 it's not an upgrade and i have the problem with dnssec ext

 

[Hangover2]

Then it would be better to open a dedicated bug report for this issue: Reports