A worked example
One code for the print server, on every device
A print server's address ends up typed into laptops, trolleys, lab images and kiosk builds across a site. Then the server moves, and all of it is wrong at once. A code is the thing you hand out instead, so the address can change without the estate changing.
The problem it solves
The address of a print server is not stable in the way the people typing it out assume. It changes when the server is replaced, when it moves to another VLAN or subnet, when a site migrates to a new host, or when somebody renames it and the old name stops answering.
Every one of those means going back to every device that was given the old address — or living with a name you no longer control because too much depends on it.
What changes
Provision once, with eight characters
Images, MDM profiles and build scripts carry a code instead of a hostname. Nothing about them has to change again when the server does.
Move the server on a Tuesday
Repoint the code and the estate follows on its next check. No reimaging, no walking a list of rooms, no waiting on a DNS change you do not control.
The internal name stays internal
A code can go on a poster in the IT office or in a handover document without the hostname going with it.
Cut one off without touching the rest
Switch a code off and everything holding it stops resolving immediately — useful when a site leaves, or a build escapes that should not have.
A trust with several schools
A group of five codes is sold as one set and works as one set: they resolve alongside each other and not alongside codes from anywhere else. One per school, renewed together, is the shape that usually fits.
A single code per site works too if the sites are unrelated — groups are about which codes belong together, not about how many you can have.
What you need for this to work
That is why this suits custom setups — a provisioning script, an MDM configuration generator, a print-release kiosk, anything you build or control. If every device is configured by hand through a vendor console you cannot script, a code will not help you.
If you are building that part yourself, the lookup is one request. Ask us for API access and tell us what you are building.
Whose server it has to be
Yours, or your organisation's, or one you are authorised to point at. We supply the code and nothing else — we do not operate, host or inspect anything at the address behind it. The short version is here.