Search results

OK, BIND on Plesk seems not compatible with new dnssec-policy's.. yesterday it was working, today named.conf ist malformed again.. Now I fixed the file manuelly and created a copy, then I created an event, that on dns-changes the copy overwrites the one from plesk.

for anyone else getting problems with new bind on 18.0.74 Here is the solution: Disable DNSSEC for all domains 1. plesk installer remove --components bind 2. apt purge bind9 bind9-utils bind9-host bind9-libs 3. apt autoremove 4. rm -rf /var/lib/bind 5. rm -rf /var/cache/bind 6. rm -rf...

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...

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'...

I fixed it on my own, Just deleted /etc/named.conf and all is working.. Don't know why this file is created, when all is working without it also just fine re-install of fresh Debian 13 was not necessary, but to late for me.. Manual upgrading using any HowTo for "Debian 12 to 13 upgrade" would...

the actual solution is, I deleted named.conf in /etc/ complete and now all is working Seems there are bugs with the situation, auto-dnssec was replaced by dnssec-policy since Bind 9.18.

Seems there is some serious problem with the Troubleshooting of this dnssec-policy Problem occured.. 2 of 3 domains were resolved, but DENIC states Errors with Nameserver, but 3rd Domain ist not resolved, I checked Nameserver in plesk and registrar, all fine but no success :/ Seems my DNS is...

Problem still exists, even after Migration from the failing server to a complete new machine. I think it can't be some conflicting file, more like error with bind itself, because plesk DNS repair in all scenarios mention, DNS hast no problems found, but it can't get startet because of mismatch...

I don't have any Debian 12 machine left running yet. Only thing possible is, setting up a fresh Debian 13 System and migrate from my actual System, which ist restored out of old upgraded system. Maybe this will fix issues, that were imported with the Backup?

Reinstalled with fresh Debian 13 and restored backup, Error still exists + Apache2 through lots of Errors, so no it was not the manual upgrade that caused the error

I'm going to install a new server based in Debian 13 and see if it fixes the issue. Even unsign DNSSEC does not fix it, because IT re-generate the file and bind can not start

Soo.. after editing the line dnssec-policy "domain123.de"; to dnssec-policy default; I was able to start dns service again, but this won't last long I think, because the file is auto generated by plesk

named-checkconf shows absolute nothing, also no error but the dnssec-policy error still existe in Journal. For all 3 dnssec-enabled domains and I believe it prevents dns from starting "dnssec-policy 'domain123.de' has no matching dnssec-policy" Here the config in /etc/named.conf: zone...

I got it.. every Domain with DNSSEC enabled get a error: "dnssec-policy doesn't match dnssec-policy config" What can I do? Re-enable DNSSEC and repair DNS dies not fix it

Hi, I upgraded to Debian 13 few days ago, after 18.0.74 was released and all was working. But today I noticed, DNS Service isn't active. But it can't get started, the only Error I get is: BIND Domain Name Server named.service Loaded: loaded (/usr/lib/systemd/system/named Drop-In...

Yes, DNSSEC ist activated for all domains and also confirmed by few online tools

Hi, I have a mysterious problem with TLSA entries in my server. Domain 1 has LetsEncrypt SSL with Dane activated and new TLSA are published immediatly. Domain 2 with same setup will mit update TLSA, even restarting DNS Server and also whole plesk didn't resolve it. What can cause this...

Hi, I have a problem, that sometimes occur with sending mail delivery confirmations failing. The mailserver try to send the delivery confirmation to the client, but this falls: "<client@pleskmailer>: host 127.0.0.1[127.0.0.1] said: 550 5.7.1 id=30096-07 - Rejected by next-hop MTA on...

Hi, I have a question about hosting a website in plesk, but the site originally ist hosted on another local server without Public IP. To show you: Website example.com is hosted on plesk to bei reached from from (local IP 10.10.10.10), but the site/service ist original hosted on Server...

But where do they cache old keys? When I update the keys and test them online, they are working within seconds