otinstaller · Domain and DNS
Install dnsgen on Linux in one command
dnsgen takes a list of known subdomains and generates plausible permutations: numbers, environments, regions, and common words. It prints candidates for a resolver to check; it does no resolution itself.
dnsgen in three lines
pipx install otinstaller
ot install dnsgen
ot run dnsgen -- d:example.comRuns AlephNullSK/dnsgen (MIT, ★ 1.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What dnsgen is for
- Expanding ctfr or BBOT output into more names to resolve.
- Finding staging and dev hosts that follow a naming pattern.
Typed inputs for dnsgen
otinstaller translates these prefixes into dnsgen's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- d:
- domain ·
ot run dnsgen -- d:example.com
Run every installed tool that takes the same input at once: ot run --all d:example.com
Where the results go
Every run lands under ./results/dnsgen/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff dnsgen <target>, and pull indicators out with ot extract.
Before you run it
- Pipe the output into a resolver such as the one in BBOT or secator; dnsgen only generates.
Update, remove, inspect
ot info dnsgen # inputs, flags, keys
ot example dnsgen # sample output
ot update dnsgen # move to the next tested version
ot remove dnsgen # delete its virtualenvFull reference for this tool: docs for dnsgen.
Pairs with
FAQ
dnsgen with otinstaller, answered
How do I install dnsgen on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install dnsgen. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.
Which inputs does dnsgen take through otinstaller?
d: (domain). otinstaller maps each prefix to dnsgen's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otinstaller save dnsgen results?
Under ./results/dnsgen/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff dnsgen <target> to compare the last two.
Does dnsgen need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.
Can I run dnsgen together with other tools?
Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including dnsgen. Save the combination as a playbook to repeat it.