KeyHelp Community

SI received a notification that Debian 12 was reaching its end of support. I followed the instructions in keyhelp for the upgrade, but it didn't work, and my server became unusable. Initially, I got a Bind error, but everything else seemed to be working correctly. Only the domains stopped working. When I restored the backup immediately prior to the upgrade, the entire server stopped working, and I can only access it via SSH.

PuntonetSvb wrote: ↑Fri 6. Mar 2026, 13:00 Initially, I got a Bind error, but everything else seemed to be working correctly.

I had the same error yesterday. I was including
/etc/bind/named.conf.default-zones
which has been removed from Trixie.

24unix wrote: ↑Fri 6. Mar 2026, 13:08

PuntonetSvb wrote: ↑Fri 6. Mar 2026, 13:00 Initially, I got a Bind error, but everything else seemed to be working correctly.

I had the same error yesterday. I was including
/etc/bind/named.conf.default-zones
which has been removed from Trixie.

And how did you solve it? I've been trying for two days straight and there's no way.

Why did you do a rollback when the nameserver is not running? You can check the logs and solve the problem.

So what is the latest state of your server? When you id a rollback and it is not wokring than something is wrong with your backup

PuntonetSvb wrote: ↑Fri 6. Mar 2026, 16:40

24unix wrote: ↑Fri 6. Mar 2026, 13:08

PuntonetSvb wrote: ↑Fri 6. Mar 2026, 13:00 Initially, I got a Bind error, but everything else seemed to be working correctly.

I had the same error yesterday. I was including
/etc/bind/named.conf.default-zones
which has been removed from Trixie.

And how did you solve it? I've been trying for two days straight and there's no way.

Run named-checkconf, it tells you the problematic file.
Remove the entry, restart bind.

It can handle root zones out of the box.