This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A subdomain you forgot is a name that still resolves. The finder and the history tools draft names for a zone you administer. You compare them with the inventory. A name you do not recognise is a ticket, not a thing you immediately browse.
This is not a permission to guess names on someone else's domain. A word list aimed at a company you do not operate is out of scope. A zone transfer is out of scope. Reverse lookups are for addresses you hold, not a walk of a range.
Write the zone, the date, and the names that were not in inventory. Then stop. Taking down a name is a DNS change with its own window and a TTL.
example.com is documentation. Substitute a zone you run, or do not run the draft.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name the zone you operate.
- Read the inventory you already have.
- Draft a comparison. Delete any zone that is not yours.
- Record names missing from inventory.
- Do not request a zone transfer.
- Do not browse or attack a surprising name. Open a ticket.
Mistakes that outlive the command
How to Find Subdomains of a Domain goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A word list against a zone you do not run.
- An AXFR.
- A reverse walk of a range you do not hold.
- Treating a found name as something to exploit.
- example.com left as the target.
Decisions to write down
One decision for How to Find Subdomains of a Domain: The zone is yours. The inventory was the comparison. No transfer was requested. Unknown names became tickets. And no one else's zone was queried as a hunt.
Checks before you call it done
Confirm this before you call the change done: The zone name is in the ticket. New names are listed. No AXFR. No foreign zone was targeted. And the next step is a ticket, not a probe. If one of those fails, stop.
Your zone only.
No zone transfer. No word list against someone else.Before you leave the device
How to Find Subdomains of a Domain ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.