DNST-NOTIFY(1)

πŸ“¦ version 0.2.0, in nixpkgs unstable

πŸ’Œ DNST-NOTIFY(1) β€” the dnst girlies' guide πŸ’Œ

okay so this is dnst-notify(1), part of the dnst manual, and bestie let me tell you it is so useful. sit down, hydrate, let's go 🫢


✨ NAME ✨

dnst-notify β€” send a NOTIFY message to a list of name servers. that's it, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

dnst notify [OPTIONS] -z <ZONE> <SERVERS>...

like, one command, servers at the end, options up front. we love a clean signature πŸ’…


πŸ’– DESCRIPTION πŸ’–

so dnst notify literally sends a NOTIFY message to the name servers you point it at.

what's it telling them? that an updated zone is available at the primaries. that's the whole point, no cap. and it's got range:

  • it can perform TSIG signatures βœ…
  • it can add a SOA serial number of the updated zone βœ…

and here's the cute bit β€” if a server already has that serial number, it will disregard the message. like, respectfully, already knew that πŸ«₯πŸ’€


πŸŽ€ ARGUMENTS πŸŽ€

  • <SERVERS>... β€” one or more name servers that NOTIFY messages will be sent to, by default on port 53. you can drop as many as you want, it's a whole list.

each name server can be specified as a domain name or an IP address. either works, we're flexible 🌈


πŸ‘‘ OPTIONS πŸ‘‘

okay this is the part where I need you to focus because there are a lot of little knobs and I want you to know every single one ⭐

  • -z <ZONE> β€” the zone to send the NOTIFY for. Mandatory. like genuinely, you cannot skip this one, it's not vibing on default 🚨
  • -I <ADDRESS> β€” source IP to send the message from. ✨
  • -I <ADDRESS> β€” source IP to send the message from. πŸ‘€ yes bestie, it's listed twice in the page. I'm not making that up, I'm not "fixing" it, I'm delivering it to you exactly as it is. iconic behaviour honestly πŸ’…
  • -s <SOA VERSION> β€” SOA version number to include in the NOTIFY message. πŸ“
  • -y, --tsig <NAME:KEY[:ALGO]> β€” a base64 TSIG key and optional algorithm to use for the NOTIFY message. the algorithm defaults to hmac-sha512. so if you're not specific about your algo, that's the one you get, no discussion πŸŽ€
  • -p, --port <PORT> β€” destination port to send the UDP packet to. defaults to 53. πŸ¦‹
  • -d, --debug β€” print debug information. turn this on when things are being weird and you need to see the receipts πŸ”
  • -r, --retries <RETRIES> β€” max number of retries. defaults to 15. so it will keep trying, fifteen whole times, that's commitment 🫢
  • -h, --help β€” print the help text. short summary with -h, long help with --help. yes there are two flavours, pick your energy πŸ’–

😭 AUTHOR 😭

NLnet Labs πŸ’œ


2024–2026, NLnet Labs


quick reminder bestie: -z <ZONE> is the one thing you cannot leave out, and if a server already has that SOA serial number it will just straight up ignore your NOTIFY. not being rude, just built different πŸ™ˆ

okay that's the page!! this was dnst version 0.2.0-alpha2, dated May 15, 2026, made with love by NLnet Labs β€” go notify somebody, you're gonna slay πŸ§šπŸ’…πŸ”₯

πŸ“¦ where this page comes from