CDNSKEY and CDS RRsets must be signed with a key represented in both the current DNSKEY and DS RRset. RFC 7344, Section 4.1.
What is the issue you’re encountering
My domain uses manually configured DNSSEC with the .hu TLD, which does not support automatic rollover via CDS/CDNSKEY. Cloudflare is still publishing these records, causing validation errors in tools like DNSViz.
What steps have you taken to resolve the issue?
The DS record is set manually at the registrar and DNSSEC is fully functional and validated. The remaining issue is the unnecessary CDS/CDNSKEY records still being published.
What feature, service or problem is this related to?
Thanks for your reply! In my case, Cloudflare is the authoritative DNS provider for kiratime.hu, and I’ve enabled DNSSEC in the Cloudflare dashboard so that it signs the zone (publishing DNSKEY, RRSIG, etc.).
Because the .hu registry doesn’t support automatic DNSSEC via CDS/CDNSKEY, I’ve manually added the DS record at my registrar using the values Cloudflare provides.
So even though the DS was added manually, I still need DNSSEC enabled on Cloudflare — otherwise it wouldn’t publish DNSSEC signatures, and the domain would fail validation.
Hence DNSSEC is working correctly, but the CDS/CDNSKEY warning is cosmetic only, what I’m trying to do now is simply suppress the automatic CDS and CDNSKEY records that Cloudflare publishes, since they’re triggering RFC 7344 Section 4.1 errors in tools like DNSViz.