What is a domain name?

A name is not the thing it names

Imagine a toy shop called “The Little Rocket.” Its name helps you remember it. A domain name, such as example.com, does a similar job online: it gives you a readable name to type.

The name is separate from the website’s pages and pictures. A lookup system called DNS helps your device find where to connect.

Two different jobs

The name helps people recognize the place. The website needs somewhere to run and store its content. Registering a name does not, by itself, create a working website.

The toy-shop comparison is only a starting point. An internet name can support more than a website, including email.

Break down an example

Consider https://learn.example.com/topics/dns/. This is a URL: an address for a resource. The scheme, https, says how to access it. The host, learn.example.com, names the service here. The path, /topics/dns/, selects a resource on that service.

Read the name from the right

In learn.example.com, the dots separate parts called labels. com is the top-level domain. example.com sits below it, and learn.example.com sits below that.

learn.example.com is itself a domain name, as well as a subdomain of example.com. “Subdomain” describes a relationship, not a different kind of name. The label learn alone is not the full subdomain name.

Compare learn.example.com with example.com/learn/: the first changes the host name; the second adds a path. A path need not correspond to a real folder on the server.

Domain versus zone

A domain is a subtree of the DNS naming hierarchy. A zone is an administratively managed portion of it. A parent can delegate responsibility for a child to other authoritative servers. That creates an administrative boundary without removing the child from the naming hierarchy.

Add a name, or delegate a zone?

Suppose the example.com zone contains an address record for blog.example.com. Adding that record does not create a separate zone.

Later, its operator delegates research.example.com using NS records pointing to the child zone’s authoritative servers. Records below that boundary, such as lab.research.example.com, can now be maintained in the child zone. Research still belongs to the example.com domain hierarchy; the delegation changes who publishes that part of DNS.

Why example.com appears here

The names example.com, example.net, and example.org are reserved for documentation. We use them to make examples recognizable without suggesting that readers should register or reconfigure someone else’s ordinary domain.

Keep the layers separate

For debugging, ask three different questions: which name is in the URL, which DNS zone publishes the needed record, and what path is being requested? A wrong page path is not automatically a DNS failure. Naming, lookup, and resource selection solve different problems.