internode.in isn't a website, an app or an internet provider. Internode is the name for the infrastructure run by Jaspreet Singh in New Delhi: the servers, network equipment and services behind his projects. Each of those machines gets a name on this domain, built from one simple pattern. There's nothing to sign up for or log in to. This page explains what the names mean.
Hello
my name is
A machine's name says where it is, what it does and whether it's live.
Most people find this page after spotting an internode.in name somewhere. Here's what that usually means.
A name like denurweb01p.node.internode.in in your server logs, a traceroute or an email header simply identifies one of Internode's machines. It doesn't mean that machine offers a public service.
Think something's wrong? Report it to us.
Wrong place, sorry. internode.in is an independent Indian domain with no connection to Internode, the Australian internet provider. We don't sell internet, broadband or any consumer service.
The format, environment codes, categories and the validation rule are all on this page, with a checker you can paste names into.
A postal address goes from country down to house number. An internode.in name does the same, packing six answers into one line, always in the same order.
Paste any internode.in name to see what it means, or to find out why it doesn't fit the pattern.
The checker only tests the pattern. It can't tell you whether a machine with that name exists, and it doesn't look anything up. Some site and role codes aren't on the public list; a name can still be valid without the checker explaining every part.
We share the pattern openly so anyone can understand a name they come across. We keep the list of what actually exists to ourselves.
Enough to read any name and to name things consistently.
Anything that would describe our actual systems.
Names turn up in logs, emails and network traces. Explaining the pattern saves people guessing, and gives anyone working on our systems one shared reference.
A full inventory would hand anyone a map of our systems. Publishing the pattern explains a name; publishing the inventory would invite attacks.
Seeing a name doesn't mean the machine accepts connections from the internet. Most don't, and examples on this page don't tell you which names are in use.
A few rules sit behind every name. They're what keep the pattern reliable.
Names are all lowercase with no hyphens or underscores inside. Each part is recognised by its position and length.
A machine keeps its name until it's retired. If its job or location changes, it's rebuilt under a new name rather than renamed.
Easy names like wiki.internode.in are just pointers to a real machine name. When a service moves, the pointer moves with it.
Machines move between cloud providers more often than they change city or job, so the provider is recorded internally instead.
A disaster-recovery copy of a live system is named as production, just at a different site.
When a machine is retired, its number isn't reused for 12 months, so old references can't point at a new machine by accident.
The public reference for the Internode Infrastructure Naming Standard, version 7. Open the part you need.
| Part | Length | What it holds |
|---|---|---|
| country | 2 letters | ISO 3166-1 country code where the machine sits, such as de, us, in. For cloud machines, the country of the provider region. |
| site | 3 letters | A specific site. The first in a city uses the city's airport code; further sites in the same city get a variant, such as fra and frb. |
| role | 2–5 characters | What it does, such as bind, mysql, web, k8s. Generic machines repeat their category. |
| instance | 2–3 digits | Which one in the series, zero-padded from 01. A third digit is used only once a series grows large. |
| env | 1 letter | The environment. Always the last character before the first dot. |
| category | subdomain | What kind of thing it is, who controls it and how it's exposed. |
The host label is at most 14 characters, well inside the DNS limits of 63 per label and 253 per name.
| Code | Environment | Used for |
|---|---|---|
p | Production | Live traffic, including disaster-recovery copies |
s | Staging | A mirror of production before release |
u | User acceptance testing | Business sign-off |
t | Test / QA | Functional testing |
d | Development | Engineering work in progress |
lnew in v7 | Load / performance | Production-sized, kept separate from it |
xnew in v7 | Experimental | Proofs of concept, throwaway setups, training |
| Code | Kind of thing |
|---|---|
node | Cloud instance. Runs on a provider's hypervisor, including VMs rented from a provider. |
host | Physical machine owned and run by Internode. |
vm | Virtual machine on Internode's own hypervisors. |
oobnew in v7 | Out-of-band management interface. |
fw | Firewall |
rt | Router |
sw | Switch |
lb | Load balancer |
stg | Storage |
db | Database |
ipb | IP block, an inventory record rather than a machine |
asn | AS number, an inventory record rather than a machine |
api | API endpoint |
node, vm and host are not interchangeable. They record who controls the hypervisor, so a VM rented from a cloud provider is always node, never vm.
Every name must match this pattern (PCRE / Python syntax). Names that fail are blocked at provisioning.
^[a-z]{2}[a-z]{3}[a-z][a-z0-9]{1,4}[0-9]{2,3}[psutdlx]\.(node|host|vm|oob|fw|rt|sw|lb|stg|db|ipb|asn|api)\.internode\.in$The pattern checks shape only. Whether a site or role code is registered is checked separately against the internal registry.
These illustrate the format. They aren't a list of names in use.
| Instead of | Use | Why |
|---|---|---|
| DENURNODE01P.node… | denurnode01p.node… | Lowercase only |
| de-nur-web01p.node… | denurweb01p.node… | No separators inside the name |
| defrabind3d.node… | defrabind03d.node… | Instance has at least two digits |
| defrabind03d.vm… (cloud VM) | defrabind03d.node… | Provider VMs are node |
| defraprodweb01.node… | defraweb01p.node… | Environment is a one-letter code at the end |
| renaming wiki01p to docs01p | move the alias | Names never change; aliases do |
node for cloud, vm for Internode hypervisors, host for bare metal.oob, and new environments l and x.vm move to v7 at their next rebuild.The complete standard, including the site and role registries, is internal. It's shared on request with people who work on Internode systems.
internode.in and the Internode infrastructure are owned and maintained by Jaspreet Singh in New Delhi, India.
To report abuse, raise a concern or ask a question, use the contact form. Please include the full name you saw and where you saw it, such as a log line or an email header.
internode.in has no affiliation, partnership or endorsement with Internode, the Australian internet provider, and isn't its successor. We don't offer internet, broadband or any retail service.
If you're a customer of that provider, please contact them directly. All trademarks belong to their owners.
Please don't use this domain or its names to impersonate us or mislead others. If you see that happening, let us know and we'll deal with it.
Like most servers, ours keep access logs for security. This page uses Microsoft Clarity to understand how it's used. See the privacy policy.
This domain is operated from India, and Indian law applies.