• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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?!
 
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?
 
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
 
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.
 
You must log in or register to reply here.

Similar threads

S
Issue BIND on Debian 13 / 18.0.74 problems with DNSSEC??
Replies
4
Views
5K
sergiosgc
S
B
Resolved Dovecot fails to start after upgrade to 18.0.73 #3
Replies
3
Views
5K
bsass
B
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
3K
sistemas@chequemotiva
S
UnS3eN
Issue httpd won't start
Replies
9
Views
6K
pleskpanel
P
Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
8K
Kaspar
K
Back
Top