DNSSEC-COVERAGE(8)

💖 DNSSEC-COVERAGE(8) — the BIND 9 girlie's guide 💖

okay so bestie, listen. this is dnssec-coverage, part of the BIND 9 lineup, and honestly? she's the friend who checks your calendar and goes "girl. your keys are gonna lapse." no cap.

---

✨ NAME ✨

dnssec-coverage — checks future DNSKEY coverage for a zone 🗓️🔑

✨ SYNOPSIS ✨

dnssec-coverage [-Kdirectory] [-llength] [-ffile] [-dDNSKEY TTL] [-mmax
TTL] [-rinterval] [-ccompilezone path] [-k] [-z] [zone...]

✨ DESCRIPTION ✨

so what she does 💅 — dnssec-coverage verifies that the DNSSEC keys for a given zone (or a whole lil set of zones) have their timing metadata set properly, so that you don't get any future lapses in DNSSEC coverage. it's giving preemptive self-care for your key rollover schedule 🫶

if zone is specified, then the keys found in the key repository that match that zone get scanned, and she generates an ordered list of the events scheduled for that key — literally the whole glow-up timeline: publication, activation, inactivation, deletion 📋✨. then the list of events is walked in order of occurrence. warnings get generated if any event is scheduled that could cause the zone to enter a state where validation failures might occur — for example, if the number of published or active keys for a given algorithm drops to zero 😭, or if a key is deleted from the zone too soon after a new key is rolled and cached data signed by the prior key hasn't had time to expire from resolver caches. not the vibe. not the vibe at all 💀

if zone is not specified, then all keys in the key repository get scanned, and all zones for which there are keys will be analyzed 👑. (Note: this method of reporting is only accurate if all the zones that have keys in a given repository share the same TTL parameters.) like, she's doing her best but she needs the tea to be consistent, yk? 🙈

---

🌸 OPTIONS 🌸

• -K directory — sets the directory in which keys can be found. defaults to the current working directory. home base 🏠
• -f file — if a file is specified, then the zone is read from that file; the largest TTL and the DNSKEY TTL are determined directly from the zone data, and the -m and -d options do not need to be specified on the command line. she'll just read it herself, main character energy 📖
• -l duration — the length of time to check for DNSSEC coverage. key events scheduled further into the future than duration will be ignored, and assumed to be correct. out of sight, out of mind, we trust the process ✨

the value of duration can be set in seconds, or in larger units of time by adding a suffix: mi for minutes, h for hours, d for days, w for weeks, mo for months, y for years. suffix slay 🎀

• -m maximum TTL — sets the value to be used as the maximum TTL for the zone or zones being analyzed when determining whether there's a possibility of validation failure. when a zone-signing key is deactivated, there must be enough time for the record in the zone with the longest TTL to have expired from resolver caches before that key can be purged from the DNSKEY RRset. if that condition does not apply, a warning will be generated ⚠️

the length of the TTL can be set in seconds, or in larger units of time by adding a suffix: mi for minutes, h for hours, d for days, w for weeks, mo for months, y for years.

this option is not necessary if the -f has been used to specify a zone file. if -f has been specified, this option may still be used; it will override the value found in the file. she said "I'll allow it" 💅

if this option is not used and the maximum TTL can't be retrieved from a zone file, a warning is generated and a default value of 1 week is used.

• -d DNSKEY TTL — sets the value to be used as the DNSKEY TTL for the zone or zones being analyzed when determining whether there's a possibility of validation failure. when a key is rolled (that is, replaced with a new key), there must be enough time for the old DNSKEY RRset to have expired from resolver caches before the new key is activated and begins generating signatures. if that condition does not apply, a warning will be generated 🔥

the length of the TTL can be set in seconds, or in larger units of time by adding a suffix: mi for minutes, h for hours, d for days, w for weeks, mo for months, y for years.

this option is not necessary if -f has been used to specify a zone file from which the TTL of the DNSKEY RRset can be read, or if a default key TTL was set using the -L to dnssec-keygen. if either of those is true, this option may still be used; it will override the values found in the zone file or the key file.

if this option is not used and the key TTL can't be retrieved from the zone file or the key file, then a warning is generated and a default value of 1 day is used.

• -r resign interval — sets the value to be used as the resign interval for the zone or zones being analyzed when determining whether there's a possibility of validation failure. this value defaults to 22.5 days, which is also the default in named. however, if it's been changed by the sig-validity-interval option in named.conf, then it should also be changed here. match her freaking energy, bestie 🎯

the length of the interval can be set in seconds, or in larger units of time by adding a suffix: mi for minutes, h for hours, d for days, w for weeks, mo for months, y for years.

• -k — only check KSK coverage; ignore ZSK events. cannot be used with -z. KSK only, we're being picky 👑
• -z — only check ZSK coverage; ignore KSK events. cannot be used with -k. ZSK only, equal opportunity ✨
• -c compilezone path — specifies a path to a named-compilezone binary. used for testing. lowkey niche but she said "for the testers" 🧪

💀 real talk: -k and -z are mutually exclusive. pick ONE. do not try to be both. she will not allow it.

---

🦋 SEE ALSO 🦋

dnssec-checkds(8), dnssec-dsfromkey(8), dnssec-keygen(8), dnssec-signzone(8) — the whole friend group, go say hi 💜

🎀 AUTHOR 🎀

Internet Systems Consortium

👑 COPYRIGHT 👑

2024, Internet Systems Consortium

---

and that's the whole page bestie 🌈💖 this was dnssec-coverage(8) from BIND 9, version 9.16.50-RH, with that 2024 Internet Systems Consortium copyright serving looks. now go check your key timing metadata before something lapses and it's giving outage 😭🫶