DNSSEC-REVOKE(8)
π DNSSEC-REVOKE(8) β like, the BIND 9 one, bestie
okay so picture this: it's a BIND 9 manual page, it's called dnssec-revoke, and it's about to make one specific key very, very revoked. buckle up π
β¨ NAME β¨
dnssec-revoke β sets the REVOKED bit on a DNSSEC key π₯
πΈ SYNOPSIS πΈ
dnssec-revoke [-hr] [-v level] [-V] [-K directory] [-E engine] [-f] [-R]
{keyfile}
like, yes, that's a lot of brackets, but it's giving "choose your own adventure" and we love her for it π
π¦ DESCRIPTION π¦
okay so here's the whole vibe: dnssec-revoke reads a DNSSEC key file, sets the REVOKED bit on that key exactly as defined in RFC 5011, and then creates a brand-new pair of key files containing the now-revoked key. she ate, honestly π
no cap β the original key gets its moment, the bit gets flipped, and you walk away with two fresh files. iconic behavior only β¨
π OPTIONS π
-hβ emits a usage message and then dips. that's it, that's the whole option π«Ά-Kdirectory β sets the directory where the key files are supposed to live. tell her where home is π-rβ says "hey, remove the original keyset files after you write the new keyset files." out with the old, in with the new π-vlevel β sets the debugging level. crank it up if you want the tea β-Vβ prints version information. the classic "who even are you" check π-Eengine β specifies the cryptographic hardware to use, when applicable. fancy π
okay so this one has lore: when BIND 9 is built with OpenSSL, this needs to be set to the OpenSSL engine identifier that drives the cryptographic accelerator or hardware service module (usually pkcs11). and when BIND is built with native PKCS#11 cryptography (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via --with-pkcs11. literally wrote that down so you'd have it word for word π§
-fβ forced overwrite, bestie. it causesdnssec-revoketo write the new key pair even if a file already exists matching the algorithm and key ID of the revoked key. no questions asked, she's going in π-Rβ prints the key tag of the key with theREVOKEbit set, but does not revoke the key. so it's like a little peek, not the whole thing π
β οΈ quick vibe check: -f will overwrite existing files that match the algorithm and key ID. that's the point, but like... know that's what you asked for π
π SEE ALSO π
dnssec-keygen(8)- BIND 9 Administrator Reference Manual
- RFC 5011
go read them, iykwim πβ¨
π AUTHOR π
Internet Systems Consortium
π COPYRIGHT π
2024, Internet Systems Consortium
okay that's the whole page, you're so welcome π and for the record β this was dnssec-revoke, BIND 9, version 9.16.50-RH, dated 2024. mwah, go revoke something responsibly πβ¨π¦
π¦ where this page comes from
- centos-stream 9: bind-dnssec-doc 32:9.16.50-13.el9 Β· MPLv2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms