This episode covers DNSSEC on the Authoritative side: the KSK and ZSK concepts, RSA and ECDSA P-256 algorithms, the RRSIG, DNSKEY, DS, NSEC, and NSEC3 records, practicing pdnsutil secure-zone and show-zone, key rotation, and publishing DS to the registrar, plus pre-signed versus online signing modes.

Until now, DNS clients could only trust answers on faith. DNSSEC changes that: every record is cryptographically signed, so the receiver can verify that the answer genuinely comes from the zone owner and wasn't altered in transit.
Episode 13 covers the Authoritative side: the KSK and ZSK concepts, signing algorithms, DNSSEC records, signing practice with pdnsutil, and how to publish the DS to your registrar. In episode 14 we'll look at the verification side in the Recursor.
DNSSEC uses two layers of keys:
KSK menandatangani DNSKEY
ZSK menandatangani record (RRSIG)
DS menghubungkan zone ke parentThis separation lets you rotate the ZSK often without changing the DS published to the registrar, while the KSK is rarely rotated.
PowerDNS supports RSA and elliptic curves:
DNSSEC adds five record types:
dig @127.0.0.1 example.com DNSKEY +noall +answer +multiline
dig @127.0.0.1 example.com SOA +dnssec +noall +answerdig +dnssec shows records along with their RRSIGs. You'll see flags on the DNSKEY: 257 marks a KSK, 256 marks a ZSK.
Signing a zone is as simple as one command:
pdnsutil secure-zone example.com
pdnsutil show-zone example.compdnsutil secure-zone creates KSK and ZSK keys then signs the entire zone. pdnsutil show-zone displays key details, serial, and the DS records that must be published. To force a specific algorithm:
pdnsutil secure-zone example.com ecdsap256sha256Keys used continuously must be rotated. ZSK rotation is routine, while KSK rotation is rare and planned because it involves changing the DS at the parent:
pdnsutil add-zone-key example.com zsk ecdsap256sha256 active
pdnsutil remove-zone-key example.com <key-id-lama>
pdnsutil rectify-zone example.compdnsutil add-zone-key adds a new ZSK in active state, then the old key is removed once its signatures are no longer used.
For the chain of trust to hold, the DS record must be published to the parent zone through your registrar:
pdnsutil show-zone example.com
pdnsutil export-ds example.compdnsutil export-ds example.com shows the DS records you copy into the registrar's panel. Without this DS, validators have no anchor point to verify your zone.
PowerDNS supports two signing modes:
pdnsutil set-zone-option example.com NSEC3NARROW 1The mode is chosen per zone via pdnsutil set-zone-option. Signature maintenance (resigning) runs automatically based on default-signing-ttl.
Episode 13 makes your zones verifiable: understanding KSK/ZSK and algorithms, reading DNSKEY, RRSIG, DS, and NSEC, signing zones with pdnsutil secure-zone, rotating keys, and publishing DS to your registrar.
Key takeaways:
pdnsutil secure-zone signs a zone; export-ds produces the DS for the registrar.In episode 14, we'll cover DNSSEC: validation on the Recursor side — enabling dnssec: process, bootstrapping trust anchors from IANA, testing with dig +dnssec, reading the AD flag, trust anchor management, and handling unsigned zones or broken signatures.