Skip to content

Free domain registration and practical DNS learning resources for everyone.

3.2 KB
Raw Blame

Domain and DNS Fundamentals

This chapter begins the general textbook. It applies to domains regardless of which registration service delegates them.

The Main Systems

A working website normally uses four separate layers:

Layer Purpose
Registration Gives a registrant control of a domain name
Authoritative DNS Publishes records for that domain
Web hosting Stores or runs website content
Certificate workflow Creates and renews HTTPS certificates

One company may offer several layers, but the technical responsibilities remain separate.

Domain Name Structure

In this example:

www.example.dpdns.org

the labels are:

www -> example -> dpdns -> org -> DNS root

DNS reads the hierarchy from the root toward the most specific name even though humans normally write the most specific label first.

Registered Domain and Zone Apex

In this book, example.dpdns.org is the registered name and the apex of the zone managed at the external DNS service.

DNS editors may represent the apex as:

@
blank field
example.dpdns.org

Follow the external DNS editor's convention. Typing a full domain into a field that automatically appends the zone can create a duplicated name.

Delegation

The registration layer delegates a child domain to authoritative nameservers using NS records in the parent hierarchy.

Parent zone
  |
  | NS records
  v
External authoritative nameservers
  |
  | zone records
  v
Website and email destinations

Delegation identifies which servers are authoritative. It does not create the website address record.

Authoritative Server and Recursive Resolver

An authoritative server publishes official data for zones it hosts.

A recursive resolver performs lookups for clients, follows delegation, and caches answers.

The DNS address configured on a laptop or router is usually a recursive resolver. It is not a nameserver hostname to submit during registration.

Resource Records

Common record types include:

  • A for IPv4
  • AAAA for IPv6
  • CNAME for aliases
  • MX for mail routing
  • TXT for verification and email policy
  • CAA for certificate authority policy
  • SRV for service discovery
  • NS for authoritative nameservers
  • SOA for zone authority information

These ordinary zone records are managed in the external authoritative DNS service used by the domain.

TTL

Time to Live tells recursive resolvers how long an answer may remain cached. TTL is measured in seconds.

Changing an authoritative record does not erase already cached answers. This is why old and new values can coexist temporarily after a planned change.

First DNS Observation

dig NS example.dpdns.org
dig SOA example.dpdns.org

Read:

  • Answer type
  • Returned hostname
  • TTL
  • Whether the query succeeded

The fictional domain may not return useful live data. Repeat the observation with a public domain you are permitted to query.

Review Questions

  1. What is the difference between registration and DNS hosting?
  2. What does delegation select?
  3. Why is a recursive resolver not entered as an authoritative NS value?
  4. Where are ordinary DNS records managed?
  5. What does a TTL affect?

Continue to Part 2: Learn DNS.