opendkim-atpszone(8)

πŸ’– opendkim-atpszone β€” the manual, but make it cute πŸ’–

okay bestie, sit down, grab a strawberry πŸ“ β€” this is opendkim-atpszone from the opendkim-atpszone(8) system manager's manual situation, and it's literally the DKIM ATPS zone file generation tool. yes. that's the whole name. it's giving very-specific-tool energy and honestly? iconic. πŸ‘‘


✨ NAME ✨

opendkim-atpszone β€” the DKIM ATPS zone file generation tool, aka the little guy who writes your zone files so you don't have to πŸŽ€


🌸 SYNOPSIS 🌸

opendkim-atpszone [-A] [-C address] [-E secs] [-h hash] [-N ns[,...]]
[-o file] [-r secs] [-R secs] [-S] [-t secs] [-T secs] [-u domain] [-v]
[dataset]

πŸ’… DESCRIPTION πŸ’…

okay so. opendkim-atpszone generates a file that's suitable for use with named(8) so you can publish a whole set of domains that are authorized as third-party signers for a local domain. that's the whole job. it's a zone-file-builder and it does it well. periodt. ✨

the dataset parameter should specify a set of data the way the opendkim(8) man page describes it. and the way that it can currently refer to is: flat files, Sleepycat databases, comma-separated lists, LDAP directories, or SQL databases. so many options bestie, we love range πŸ¦‹

so the keys in that named database β€” those are assumed to comprise a set of domains that are to be advertised using the experimental Authorized Third-Party Signers protocol, as permitted to sign mail using DKIM on behalf of the local domain. meanwhile the values in the database? not used. they're just vibing. πŸ’€


πŸŽ€ OPTIONS πŸŽ€

  • -A β€” adds a ._atps suffix to records in the zone file. tiny suffix, big difference πŸ’–
  • -C contact β€” uses contact as the contact information to be used when an SOA record is generated (peep -S below πŸ‘€). if you don't specify it, the userid of the executing user plus the local hostname get used instead. and if the executing user can't be determined? you get "hostmaster". mystery user behavior fr fr.
  • -E secs β€” when generating an SOA record (again, -S below), use secs as the default record expiration time. the default is 604800. mark it. ⭐
  • -h hash β€” specifies which SHA hash algorithm to use. must be one of "none", "sha1" and "sha256", and "sha256" is the default if it's available. slay, sha256, we love a main character default 🌈
  • -N nslist β€” specifies a comma-separated list of nameservers, which get output in NS records before the TXT records. the first nameserver in this list will also be used in the SOA record (if -S is also specified) as the authority hostname. first one up gets the crown πŸ‘‘
  • -o file β€” sends output to the named file instead of standard output. no more terminal scrolling bestie 🫢
  • -r secs β€” when generating an SOA record (yes, -S, below), use secs as the zone refresh time. the default is 10800.
  • -R secs β€” when generating an SOA record (-S!! below!!), use secs as the zone retry time. the default is 1800.
  • -S β€” asks for an SOA record to be generated at the top of the output. the content of this output can be controlled using the -E, -r, -R, and -T options. the serial number will be generated based on the current time of day. clock-based serial, very on-the-nose of it πŸ•
  • -t ttl β€” puts a TTL (time-to-live) value of ttl on all records output. the units are in seconds.
  • -T secs β€” when generating an SOA record (say it with me: see -S below), use secs as the default record TTL time. the default is 86400.
  • -u domain β€” produces output suitable for use as input to nsupdate(8) to add ATPS records to the named domain. pipeline queen behavior πŸ’œ
  • -v β€” increases the verbosity of debugging output written to standard error. louder = more info, and it goes to stderr, no cap πŸ”₯

⭐ VERSION ⭐

this man page covers the version of opendkim-atpszone that shipped with version 2.11.0 of OpenDKIM. yes, we're citing our sources, we're academic like that 🧚


Copyright (c) 2011, 2012, The Trusted Domain Project. All rights reserved.


πŸ‘€ SEE ALSO πŸ‘€

nsupdate(8), opendkim(8), opendkim.conf(5) β€” go read them, bestie, they're the extended universe πŸ¦‹


and that's the whole page!! written by The Trusted Domain Project, dated in the era of the opendkim-atpszone(8) manual, for the System Manager's Manual section. mwah. go generate some zone files, you absolute legend πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from