Every name on the internet ends with the same kind of piece: .com, .org, .in. That ending is called a top-level domain, a TLD, and it is not decoration. It decides which servers answer for your name, who runs those servers, and how a name gets registered in the first place. This lesson reads a name right to left and shows where each piece comes from.
Difficulty: Beginner · Know this first: F20 — DNS: Names to Numbers
Every step charges a little time or a little money. The bar below is a worked example for this lesson's scenarios, not a measurement from a live system. The shape is honest: the check is cheap, the register step is the one that costs, and a taken name stops the walk early. Step through the lesson or switch the scenario and watch the bar change.
Extra diagram · from scratch to master
Start with the root. Add one level at a time until the whole family tree of www.example.com is on the map.
Extra diagram · from scratch to master
Start with an idea. Add one step at a time until the name is live, and see where it can fail.
Type a domain name and the simulator splits it into its pieces: subdomain, registered name, and TLD. It tells you whether the ending is generic or country, and who runs that registry. The registry facts are the real ones for the endings listed. Anything else is labeled unknown, not guessed.
Type any name with a dot in it. Try shop.example.org, site.in, or mail.google.co.uk and watch the split change.
Try this: (1) www.example.com. Subdomain www, registered name example, TLD .com, generic, registry Verisign. (2) site.in. No subdomain, registered name site, TLD .in, country (India), registry NIXI. (3) mail.google.co.uk. Subdomain mail, registered name google, TLD .uk, country (United Kingdom), registry Nominet. Note the .co in the middle: under .uk, the registered name sits under .co.uk, and the simulator says so.
Three questions. No score is saved anywhere — this is just you against the material.
I take the same idea four times here. First I learn what it is and why it exists. Then I learn to use it and read what it tells me. Then I design with it so one failure cannot take the system down. Last I run it for the world.
Definition: A domain name reads right to left: the TLD is the last part, the registered name sits under it, and the subdomain sits under that. A generic TLD like .com is not tied to a country. A country TLD like .in belongs to a place. The root is the silent dot at the end.
Types:
Uses: I use this when someone shows me a domain name. I split it in seconds and I know which registry and which servers to ask about.
Dimensions: At low traffic a name is just a label. What breaks first is picking a name that is already taken, and I notice it at the availability check, before any money moves. It costs nothing to learn the split. It costs a rebrand to learn it late. The trade is simple: a short name is easy to remember and hard to find free.
Definition: A registrar sells you the registration. The registry records it. The registration is a rental by the year, and the renewal price is the real price. Your nameserver holds the records for your name and its subdomains. The TLD servers point to your nameserver, and the root points to the TLD.
Types:
Uses: I use this when I register or move a domain. I read the renewal price, I set the nameservers, and I check the registry's own lookup before I trust the dashboard.
Dimensions: As a company grows, the number of names grows with it, and each one has a renewal date. What breaks is a name expiring quietly, and I notice it when the site and the mail die together. It costs a calendar with renewal alerts seen by more than one person. The trade is that a name costs little per year and everything when it lapses.
Definition: At this level I manage a portfolio of names: the main name, the country endings for each market, the defensive registrations that stop impersonators, and the subdomains that point at different systems. I know which endings need local presence and which do not. I plan moves around the TTL, and I keep the registration details current so a renewal notice reaches a real person.
Types:
Uses: I use this when a company expands to a new country or launches a new product. I check the local ending's rules before I promise a launch date.
Dimensions: At ten times the names, the risk is not technical, it is administrative: a contact who left, an email nobody reads, a card that expired. What breaks is the renewal notice going nowhere, and I notice it from a monitoring check, not from the registrar. It costs one owner per name and one shared calendar. The trade is that more names mean more surface to protect, and each one needs the same care as the main name.
Definition: At this level a domain name is treated like a power contract: monitored from outside, renewed years ahead, locked against transfer, and watched for lookalike registrations. I know the registry for every ending I depend on, I have the registrar's transfer lock on, and I have tested what happens when a name is attacked, hijacked, or left to expire.
Types:
Uses: I use this when a name is the business: I monitor resolution from outside networks, I alert on expiry at 90, 30, and 7 days, and I keep the recovery path written down.
Dimensions: At a hundred times the traffic a domain is still one record in one registry, and that is the point. What breaks is the single administrative thread: one person, one email, one card. I notice it by auditing the contacts, not by waiting for an outage. It costs a yearly audit and the discipline to keep it boring. The trade is that names are the cheapest critical infrastructure you own, and the easiest to lose by accident.
The root zone is a small file with a large job. It lists every TLD and the nameservers that answer for it. When a new generic ending is added, that file changes, and the change flows to every root server in the world. The list is public. Anyone can read it.
Second-level endings like .co.uk exist because some country registries only sell names under a second level. Under .uk, you register google.co.uk, not google.uk, in the classic setup. That is why the simulator treats .co.uk as one TLD for the split. Other country endings sell directly at the second level. The rule belongs to the country, not to DNS.
New generic endings are a business as much as a technical change. A company applies to run an ending, pays a large fee, and operates the registry. That is why some endings cost a few dollars a year and others cost hundreds. The price is the registry's choice, inside the rules of its contract.
Domain tasting and squatting are the two misuses worth knowing by name. Squatting is registering a name someone else wants, hoping to sell it back. Tasting was registering names in bulk during a free grace period and keeping only the ones that earned traffic. Registries closed most of the tasting loophole years ago. Squatting is still a legal fight, not a technical one.
At 10x the traffic, the shape holds. The TLD servers answer the same way whether a name gets one question a day or one a second. The registry is built for that. What grows is your own list of names, and the renewals that come with them.
At 100x, the design changes in one place only: the names are monitored like any other dependency, from outside the network, with alerts on expiry and on unexpected record changes. A name that changes without a ticket is an incident, not a curiosity.
A small team's website and email both went dark on a Monday morning. The servers were up. The DNS records were correct. Nothing had changed in weeks. The site just stopped resolving, and the mail started bouncing.
Three things. First, renewal alerts go to a shared inbox that more than one person reads, and the expiry date is a calendar event. Second, critical names are renewed for five years at a time, not one, so a missed email cannot kill them in a year. Third, an outside check watches the domain itself, not just the site: if the name stops resolving, it pages. A server can be perfect and still be unreachable, because the name is the front door, and the front door was rented, not owned.
Design the domain setup for a company launching a shop in India and the UK, with a main site, an API, and mail. The company name is already taken under .com.
Start with the count. Three markets means at least three registered names, plus subdomains for the site, the API, and mail under each one. Subdomains cost nothing, so the count that matters is the registered names: three renewals a year, three expiry dates, three sets of local rules. The .in registration follows NIXI's rules and the .uk follows Nominet's. A five-year renewal on each one turns three yearly risks into three risks every five years.
More endings buy local trust and cost more renewals to track. A single global name is simpler and weaker in each market. Defensive registrations buy protection from lookalikes and cost money for names you will never use. And the .com problem is a naming decision, not a technical one: a different name that is free everywhere beats a perfect name that belongs to someone else.