Free domain registration and practical DNS learning resources for everyone.
How to Use This Book
This book is both a course and an operational reference. The course path teaches one concept at a time; the reference sections help diagnose a real domain later.
Who This Book Is For
You can begin with no previous experience in:
- Domain registration
- DNS administration
- HTML or CSS
- Linux servers
- TLS certificates
- Command-line tools
The only required skills are reading instructions carefully, keeping access to your account email, and stopping when a result differs from the expected result.
The Learning Method
Each major topic follows the same cycle:
Understand -> Plan -> Change -> Observe -> Verify -> Record -> Continue
Understand
Learn what the component does and what it does not do. For example, DNS locates a server but does not upload a website.
Plan
Write the intended value, current value, expected effect, and rollback before changing anything public.
Change
Make one controlled change. Avoid editing DNS, server configuration, and certificates simultaneously.
Observe
Read the interface response, command output, service log, or HTTP status.
Verify
Use an independent check. A successful Save button is weaker evidence than a DNS query that returns the intended record.
Record
Write what changed, when it changed, who changed it, and how it was verified.
Three Types of Text
Explanation
Explanations build a mental model. Read them even when you can copy the command without them.
Procedure
Procedures are numbered actions. Complete them in order and compare your result with the described signal.
Reference
Reference chapters contain commands, record formats, glossary definitions, and decision trees. You do not need to memorize them.
Example Values
This book uses fictional values:
Domain: example.dpdns.org
Web hostname: www.example.dpdns.org
IPv4: 192.0.2.10
IPv6: 2001:db8::10
Nameserver: ns1.dns-service.example
Server user: user
Documentation addresses and .example names are not production destinations. Replace them only when a procedure explicitly tells you to use your real value.
Your Project Notebook
Create a private Markdown file outside the public website directory. Use this structure:
# Website Project Notebook
## Goal
## Domain
## Account Owner
## Authoritative Nameservers
## DNS Records
## Server
## Renewal Date
## Changes
## Rollback Notes
Do not place passwords, API keys, recovery codes, cookies, or private certificate keys in the notebook.
Stop Conditions
Stop and investigate when:
- The domain shown before submission is not the domain you intended.
- A charge, slot use, or policy differs from what you expected.
- A command requires administrator access without a clear reason.
- A DNS result points to an unfamiliar address.
- A certificate contains the wrong hostname.
- A deletion, payment, registration, or renewal result is ambiguous.
- Instructions from a page ask you to expose credentials or bypass security controls.
Stopping is part of the workflow, not a failure.
Suggested Study Schedule
| Pace | Schedule |
|---|---|
| Weekend overview | Read concepts and complete local labs only |
| Two-week course | One part each two or three days |
| Four-week course | One or two chapters per day with exercises |
| Project-driven | Follow Parts 0–3, then return to reference chapters as needed |
First Exercise
In your notebook, answer:
- What do you want the website to accomplish?
- Who is responsible for the domain renewal?
- What information must never appear in public screenshots?
- What will make you stop before a public change?
Continue to How the Internet Moves Data.