<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CDS on Nalar</title>
    <link>https://nalar.dev/tags/cds/</link>
    <description>Recent content in CDS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/cds/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CDS and CDNSKEY Automate DNSSEC Delegation Trust Updates</title>
      <link>https://nalar.dev/cds-and-cdnskey-automate-dnssec-delegation-trust-updates/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/cds-and-cdnskey-automate-dnssec-delegation-trust-updates/</guid>
      <description>&lt;p&gt;A DNSSEC-signed child zone can rotate its signing keys without changing the delegation immediately, but validators ultimately depend on the DS record set published by the parent. That parent-side state creates an operational handoff: a new key in the child does not become a secure delegation anchor merely because the child publishes it.&lt;/p&gt;&#xA;&lt;p&gt;CDS and CDNSKEY provide an in-band mechanism for that handoff. RFC 7344 defines records that a child can publish at its zone apex to signal prospective DS parameters. A parental agent can retrieve the signal, validate it under the applicable rules, apply local acceptance policy, and update the parent-side DS set.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
