REALMINIT(1)
π¦ REALMINIT(1) β or, how to birth brand-new realms β¨
okay so bestie, this is a page from the User Contributed Perl Documentation section, and it's literally all about realminit. Let's get into it π
β¨ NAME β¨
realminit β creates new realm records for a DNSSEC-Tools realms file. that's the whole vibe π
πΈ SYNOPSIS πΈ
realminit [options] <realm1> ... <realmN>
π DESCRIPTION π
So realminit makes brand-new realm entries for a realms file. And what's a realm, you ask? okay so dtrealms is out here managing multiple distinct DNSSEC-Tools rollover environments running at the same time β and each one of those rollover environments is called a realm, and it gets defined in a realms file. dtrealms reads that file to figure out how to run the rollover environment. it's giving very useful, honestly β think managing absolutely massive collections of zones, keeping customer zones segregated, and software tests. iconic use cases fr fr π
The newly generated realm entries get written to standard output β unless you hit it with the -out option. noted π
A realms file has a bunch of entries, one for each managed realm. each realm entry looks exactly like this:
realm "example"
state "active"
configdir "/usr/realms/configs/example"
statedir "/usr/realms/states/example"
realmsdir "/usr/realms/realms-files/example"
rollrec "example.rrf"
administrator "bob@cat.example.com"
display "1"
manager "rollerd"
args "-display -loglevel phase"
You can create multiple realm entries with a single execution of realminit π«Ά. Except for the entry's name field, those entries will be exactly the same β unless you use the '=' metacharacter in the command-line options. Here's the tea: if the values of the configdir, statedir, realmdir, rollrec, administrator, args, or user options contain an '=', then that '=' gets replaced with the realm's name when the entry is built. the EXAMPLES section down below shows exactly how options get used by realminit, so don't worry β¨
π OPTIONS π
realminit may be given the following options:
-activeβ this saysdtrealmsshould start the realm wheneverdtrealmsstarts. and lowkey realms are active by default, so this is the default vibe already.-administratorβ the email address for the realm's administrator π§-argsβ a set of command-line arguments that get passed to the realm's rollover manager when the realm is started.-configdirβ the realm's configuration directory. this is where stuff like the DNSSEC-Tools configuration file for that realm lives πΈ-displayβ says whether the realm should be included ingrandvizieroutput.-inactiveβ this saysdtrealmsshould not start the realm whendtrealmsstarts.-managerβ the rollover manager for the realm.rollerdis the default rollover manager, but other managers may be used.-outoutput-file β the new realm entries get appended to output-file. the file gets created if it doesn't already exist π
If this option is not given, the new rollrec entries will be written to standard output.
-realmdirβ the realm's data directory. this directory is expected to contain the rollrec file, zone files, keyrec files, and key files for the zones in that realm.-rollrecβ the path to the realm's rollrec file. this is what's used to control rollover actions for the realm. if it's not an absolute path, it will be assumed to be relative to therealmdirfield.-statedirβ the realm's state directory. this holds stuff like that realm's rollrec lock file and therollerdcommunications socket. and ifstatedirisn't defined for a realm, then the realm'sconfigdirgets used for that value π-userβ the user that the realm is executed as. (not yet implemented indtrealms, just so you know π)-helpβ display a usage message.-Versionβ display version information forrealminitand DNSSEC-Tools.
π EXAMPLES π
these options should make it super clear how realminit deals with options and the new realms. Example 1 shows the complete new realm record. for the sake of brevity, the remaining examples only show the fields relevant to that example. and further examples also use short-hand forms of the option names β iykyk π
π Example 1. One realm, with -statedir
this example shows the realm you get by giving realminit a single realm.
$ realminit -active -configdir /realms/confs/example -statedir /realms/states/example -realmdir /realms/realms/example -rollrec example.rrf -admin bob@cat.example.com -args "-loglevel phase -logfile logger" example
realm "example"
state "active"
configdir "/realms/confs/example"
statedir "/realms/states/example"
realmdir "/realms/realms/example"
rollrec "example.rrf"
administrator "bob@cat.example.com"
display "1"
manager "rollerd"
args "-loglevel phase -logfile logger"
π¦ Example 2. One realm, without -statedir
this example shows the realm you get by giving realminit a single realm.
$ realminit -active -configdir /realms/confs/example -realmdir /realms/realms/example -rollrec example.rrf -admin bob@cat.example.com -args "-loglevel phase -logfile logger" example
realm "example"
state "active"
configdir "/realms/confs/example"
statedir "/realms/confs/example"
...
β Example 3. Two realms, without metacharacters
this example shows the realms you get by giving realminit two realms, without using the special "=" metacharacter.
$ realminit -configdir /realms/confs/example -statedir /realms/states/example -realmdir /realms/realms/example -rollrec example.rrf -admin bob@cat.example.com example test
realm "example"
configdir "/realms/confs/example"
statedir "/realms/states/example"
realmdir "/realms/realms/example"
rollrec "example.rrf"
administrator "bob@cat.example.com"
...
realm "test"
configdir "/realms/confs/example"
statedir "/realms/states/example"
realmdir "/realms/realms/example"
rollrec "example.rrf"
administrator "bob@cat.example.com"
...
π Example 4. Two realms, with metacharacters
this example shows the realms you get by giving realminit two realms, and that uses the special "=" metacharacter. this is where it gets good π₯
$ realminit -configdir /realms/confs/= -statedir /realms/states/= -realmdir /realms/realms/= -rollrec =.rrf -admin bob@cat.=.com example test
realm "example"
configdir "/realms/confs/example"
statedir "/realms/states/example"
realmdir "/realms/realms/example"
rollrec "example.rrf"
administrator "bob@cat.example.com"
...
realm "test"
configdir "/realms/confs/test"
statedir "/realms/states/test"
realmdir "/realms/realms/test"
rollrec "test.rrf"
administrator "bob@cat.test.com"
...
π COPYRIGHT π
Copyright 2012-2014 SPARTA, Inc. All rights reserved. see the COPYING file included with the DNSSEC-Tools package for details, bestie π
π§ AUTHOR π§
Wayne Morrison, tewok@tislabs.com β legend behavior honestly π«Ά
π SEE ALSO π
lsrealm(1),dtrealms(8),realmchk(8)Net::DNS::SEC::Tools::realm.pm(3)file-realmrec.pm(5)
okay and that's the whole page, mwah π β this lil doc came to you courtesy of perl v5.44.0, dated 2026-10-17, and filed under REALMINIT(1). go forth and make realms, bestie πβ¨
π¦ where this page comes from
- arch rolling: dnssec-tools 2.2.3-16 Β· BSD
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms