DTREALMS(1)

πŸ“¦
version 2.2.3 Β· 2 versions
, in fedora 43

πŸ’– DTREALMS πŸ’– (that's the dtrealms manual page, section 1, from the User Contributed Perl Documentation crew, bestie)

okay so listen. this is dtrealms, a Perl thing that shows you the defaults defined for DNSSEC-Tools. buckle up, it's a whole vibe.


✨ SYNOPSIS ✨

dtrealms [options] <realm-file>

πŸ¦‹ DESCRIPTION πŸ¦‹

ngl dtrealms is out here managing multiple distinct DNSSEC-Tools rollover environments all running at the same time. each one of those environments is called a realm, and every realm gets defined in a realms file. dtrealms reads that file to figure out how the rollover environment has to be initialized so it can run independently from all the other rollover environments on that particular system. it's giving very much "divide and conquer" ✨ this is useful for stuff like managing absolutely gigantic collections of zones, segregating customer zones, and software tests.

the realms file can be created with realminit. rn the distinct environment for each realm has to be created manually 😭 but the hope is that a tool will soon be available to help with creating each realm's environment. fingers crossed fr fr.

also like, dtrealms isn't actually necessary for running multiple realms. but it does make it way easier to manage multiple realms running consecutively. it's the helpful bestie of the group.


πŸŽ€ REALM SETUP πŸŽ€

a realm is primarily defined by its entry in a realms file. four fields in particular describe where the realm's files are located and how it runs. these are the realm's configuration directory, state directory, realm directory, and rollrec file. these directories are used to set the DT_STATEDIR and DT_SYSCONFDIR environment variables, and the rollrec file defines which zones are managed by the realm's rollover manager.

https://www.dnssec-tools.org/wiki/index.php/Rollover_Realms:_Multiple,_Simultaneous,_Independent_Rollover_Environments has more information on creating realms. (iykyk, go read it πŸ’œ)

configdir

the configdir field of the realms file contains the name of the realm's configuration directory. this file gives command paths and configuration values for running the DNSSEC-Tools. the DNSSEC-Tools modules expect this directory hierarchy to contain a dnssec-tools subdirectory, and a dnssec-tools.conf file within that subdirectory. the path fields in the configuration file point to various things, such as commands and key archives. it is recommended that these paths only point within the configdir hierarchy, other than for system utilities. πŸ‘‘

the DT_SYSCONFDIR environment variable is set to the configdir field. this will tell the DNSSEC-Tools programs and modules where to find their required data.

statedir

the statedir field of the realms file contains the name of the realm's state directory. this directory contains such files as the rollrec lock file and the rollerd communications socket. if a realm definition does not contain a statedir field, then that realm will use the configdir field as its statedir field.

the DT_STATEDIR environment variable is set to the statedir field. this will tell the DNSSEC-Tools programs and modules where to find these files.

realmdir

the realmdir field of the realms file contains the name of the directory in which the realm executes. this is where the realm's zone, key, and other files are located. πŸ“

rollrec

the rollrec field of the realms file is the name of the file that controls zone rollover. this file points to the various keyrec files that define the locations of the zone files and their associated key files. a realm's rollrec file can locate these files anywhere on the system, but it is strongly recommended that they all remain within the realm's realmdir hierarchy. 🫢

while the DNSSEC-Tools programs will work fine if a realm's configuration, state, and realm directories are actually one directory, it is recommended that at the least the realmdir files be separated from the configdir and statedir files.

it is further recommended that the files for the various realms be segregated from each other. keep them apart, bestie, it's the healthy thing to do πŸ’…


πŸ”₯ OPTIONS πŸ”₯

the following options are handled by dtrealms.

  • -directory β€” directory in which dtrealms will be executed. any relative paths given in realms configuration files will use this directory as their base.
  • -display β€” start the grandvizier display program to give a graphical indication of realm status. so you can see the vibe πŸ‘€
  • -foreground β€” run dtrealms in the foreground instead of as a daemon.
  • -logfile β€” logging file to use.
  • -loglevel β€” logging level to use when writing to the log file. see rolllog(3) for more details.
  • -logtz β€” time zone to use with the log file. this must be either "gmt" or "local".
  • -Version β€” displays the version information for dtrealms and the DNSSEC-Tools package.
  • -help β€” displays a help message and exits.

😭 WARNING 😭

this is an early prototype. consider it to be beta quality. so like... be gentle with it, okay? it's doing its best πŸ₯Ί


Copyright 2011-2014 SPARTA, Inc. All rights reserved. See the COPYING file included with the DNSSEC-Tools package for details.


🌸 AUTHOR 🌸

Wayne Morrison, tewok@tislabs.com


🌈 SEE ALSO 🌈

  • grandvizier(8)
  • lsrealm(8)
  • realminit(8)
  • realmset(8)
  • Net::DNS::SEC::Tools::realm.pm(3)
  • Net::DNS::SEC::Tools::realmmgr.pm(3)
  • Net::DNS::SEC::Tools::rolllog.pm(3)

okay that's the whole page, bestie πŸ’– this one was brought to you by perl v5.42.0, dated 2025-07-23, and honestly? iconic. periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from