• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question DNSSEC - The TTL of the RRset exceeds the value of the Original TTL field of the RRSIG RR covering it

psxeu

Basic Pleskian
Server operating system version
Almalinux 9
Plesk version and microupdate number
Plesk Obsidian 18.0.67
Hi

I am setting DNSSEC up and are using a couple of online services to validate if everything is okay. One of the services are DNSViz | A DNS visualization tool - When I do it for a domain I get some errors:

RRSIG NSEC proving non-existence of MyDomain.tld/CDNSKEY alg 14, id 47160: The TTL of the RRset (10800) exceeds the value of the Original TTL field of the RRSIG RR covering it (7200). See RFC 4035, Sec. 2.2.

I can fix it by setting the Zone defaults TTL to 3 hours - but it seems more like a hack. Should the system not align the TTL for the RRset with the Zone defaults TTL?
 
I am not able to replicate this issue but then again I'm using Debian 12 instead of AlmaLinux. I'm wondering if this is something the registrar is doing?
 
Back
Top