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
Reverse DNS maps an address back to a name. You can set the PTR when you administer the reverse zone, or when the provider gives you a form for an address they assigned to you. The lookup shows what is published now. It does not change it.
An address in 192.0.2.0/24 is documentation. Do not file a PTR for an address you do not hold. A name you do not control is not a PTR you invent so a mail test looks green.
Write the address, the name, and who holds the reverse zone. The change, if it is yours, waits for that owner's window. This page stops at the plan.
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.
- Look up one address you may hold.
- Write the current PTR.
- Name who holds the reverse zone.
- Do not invent a name you do not control.
- Do not edit a zone in this hour.
- Stop after one address.
Mistakes that outlive the command
How to Set Up Reverse DNS (PTR) goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A PTR for an address you do not hold.
- A documentation address filed as production.
- Editing a provider zone from a guess.
- A name you do not administer used to pass a check.
Decisions to write down
One decision for How to Set Up Reverse DNS (PTR): The address is yours or documentation. The zone owner is named. The desired name is one you control. Nothing was edited. And one address is the scope.
Checks before you call it done
Confirm this before you call the change done: The current PTR is written. The owner is written. The desired name is written. No zone was changed. And a second person agrees the address is yours. If one of those fails, stop.
Before you leave the device
How to Set Up Reverse DNS (PTR) 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.