What Is a Domain Name? How Domains Actually Work

A domain name is the readable address people type to reach something on the internet. That much is obvious. What is less obvious, and what causes most of the expensive mistakes people make with domains, is what you are actually getting when you register one.

You are not buying a piece of the internet. You are taking out a time-limited lease on an entry in a database, and that entry does nothing except point at other machines. Everything that makes domains confusing follows from those two facts.

You are leasing, not buying#

Nobody owns a domain name outright. You hold the exclusive right to use it for a fixed term, usually one to ten years, and you renew to keep that right. Stop paying and it goes back into circulation for someone else to register.

This is why "buy a domain" is a slightly misleading phrase that the entire industry uses anyway. There is no deed. There is a registration record with an expiry date on it, and your name in the registrant field.

The practical consequence is that a domain is only as safe as its renewal. Names with real businesses on them are lost every year to an expired card on a forgotten account, not to anything dramatic.

The three parties#

Almost every domain question becomes easier once you know which of these three you are dealing with.

There is exactly one registry per extension and it is not a choice you make. Every .com in the world lives in Verisign's database no matter who you bought it from. Registrars compete on price, interface and support, but the underlying record is identical.

That single fact explains a lot. It is why moving between registrars does not change your domain, why a registrar cannot invent rules the registry forbids, and why some locks can be removed by your registrar while others cannot be removed by anyone.

Reading a domain name#

Domains are read right to left, from the most general part to the most specific.

The important line in that table is the last one. Subdomains are free and unlimited. Once you hold example.com you can create shop.example.com, blog.example.com and app.example.com without registering anything or paying anyone. People routinely register extra domains for things a subdomain would have handled.

What happens when someone types your domain#

Domains exist because machines route by IP address and humans do not remember numbers. The Domain Name System is the translation layer, and it runs on every request you make.

Here is the full sequence, which normally completes in well under a second:

1. The browser checks its own cache. If it resolved your name recently, it stops here.
2. The operating system checks its cache, and the hosts file if there is an entry.
3. The resolver takes over. This is usually your ISP's, or a public one like 1.1.1.1 or 8.8.8.8. If it has a fresh answer cached, it returns it and stops.
4. The resolver asks a root server where to find the extension. The root does not know your domain. It knows who runs .com and says so.
5. The resolver asks the .com nameservers about your domain. The registry does not know your IP address either. It knows which nameservers you delegated to and says so.
6. The resolver asks your nameservers, which hold the actual records, and gets the IP address back.
7. The browser connects to that IP and asks for the page.

Two things in that chain surprise people. The registry never stores your website's address, only a pointer to your nameservers. And most lookups never reach step 4, because caching absorbs almost all of the traffic.

Nameservers are the switchboard#

Your nameservers are the single most consequential setting on a domain. They decide which machines get to answer questions about your name, and therefore where all of your traffic and email go.

Change them and you move the entire domain to a different DNS provider in one step. This is also why an unexpected nameserver change is the most serious warning sign in domain security. Anyone who controls your nameservers controls your website and can receive your email, without ever touching your registration.

If you are watching a name you care about, nameservers are the field to watch. Domain Hub records a before and after value on every change for exactly this reason.

The records you will actually meet#

Nameservers hold a zone, and a zone holds records. You will meet perhaps six in normal use.

MX is worth singling out because it is completely independent of your website. Your site can be on one provider and your email on another, and neither knows about the other. This is why setting up an address at your own domain is a separate job from building the site, and why deleting the wrong record silently stops your mail rather than breaking your homepage.

Propagation is mostly caching#

When you change a record and someone tells you to wait for propagation, almost nothing is propagating. Your nameservers updated immediately. What you are waiting for is every cache in the chain to let its old copy expire.

That expiry is controlled by the TTL on the record, measured in seconds. A TTL of 3600 means resolvers may keep the old answer for an hour after you changed it.

The practical trick: lower the TTL to a few minutes at least a day before a planned migration. Then the switch itself takes minutes instead of hours. Raise it again once the move is settled.

Nameserver changes are the exception. Those are delegated at the registry and genuinely can take longer to settle everywhere.

Domain, hosting and website are three different purchases#

This is the most common beginner confusion, and it costs people money.

They are frequently sold together, which is where the confusion comes from. They do not have to be, and keeping them separate is usually the better arrangement. Your domain is the one asset that is genuinely portable. Hosting can be replaced in an afternoon. A domain with years of links and traffic behind it cannot be replaced at all.

Register the name somewhere you trust, keep it separate from your hosting, and you can change everything else later without touching it.

What you actually control#

Once a name is registered to you, you control four things:

• The registrant record, meaning who the domain belongs to
• The nameservers, meaning who answers for it
• The DNS records, if you use your registrar's nameservers
• Whether it renews, which is the one that quietly matters most

You do not control the registry's rules, the extension's pricing, or the status codes the registry applies. Those come from above and no amount of arguing with support will change them.

Three misconceptions worth dropping#

"I bought it, so it is mine forever." It is yours until the expiry date. Renewal is the whole game.

"An expired domain is available." It is not. Expiry starts a lifecycle of roughly 75 to 80 days across grace, redemption and pending delete before the name is released. The details are worth knowing if you are waiting on one.

"Availability means it is safe to use." Availability is a registry question. Whether you can safely trade under a name is a trademark question, and the two are unrelated. A name can be free to register and still be one you must not use.

Where to go next#

If you have the concepts and want a name, the domain checker tests availability across extensions at once, and the name generator helps when you have a concept but not a word yet.

If you already hold names, the thing worth setting up early is monitoring, because expiry and nameserver changes are the two failures that cost real money and neither one announces itself.