Point the root recordThe root domain usually needs an A record to the VPS IP. dig +short example.com A returns the expected IP.
Domains and HTTPS
DNS Records and SSL for Makers
Learn the practical order for pointing a domain at a VPS, checking DNS, proving HTTP, and adding HTTPS.
Ladder steps
Each step should prove one idea before the project asks for the next one.
Point www deliberatelywww can be a CNAME to the root domain or its own A record. dig +short www.example.com returns a sensible answer.
Serve HTTP firstCertificate issuance is easier after port 80 answers correctly. curl -I http://example.com returns the expected site.
Add HTTPS lastTLS should be configured after DNS and HTTP are already proven. curl -I https://example.com returns 200 or redirect as intended.
Examples to inspect
Use examples to read signals, not as blind recipes.
Check the root A record
dig +short topicladder.com AExpected signal: The VPS IPv4 address
Check the www answer
dig +short www.topicladder.comExpected signal: A CNAME or resolved IP
Verify public HTTP
curl -I http://topicladder.com/Expected signal: A status line and server headers
Common traps
- Changing DNS and TLS at the same time.
- Testing only from the VPS.
- Forgetting www when issuing certificates.
Practice task
Write the sequence you would use to connect a new domain to an existing VPS, including the command that proves each step.
Next steps
- Learn Nginx static roots.
- Learn release symlinks.
- Learn Search Console setup when the site is ready.
Practice ladder
- Near-Copy Rebuild: Recreate one example, decision path, or worked explanation from DNS Records and SSL for Makers. Keep most givens the same, then apply, explain, and check while naming each cue you used. Use the lesson's example block when it helps.
- One-Change Transfer: Change exactly one condition, number, input, symptom, material, or constraint from the near-copy case. Then apply, explain, and check again and explain what changed.
- Mixed Review Set: Interleave this topic with one prerequisite or adjacent idea. Write three short prompts: one recall, one application, and one comparison.
- Find And Fix The Error: Invent a plausible wrong answer, unsafe step, invalid assumption, or bad classification. Mark the first point where it goes wrong, then correct it using the lesson's check.
Flashcard preview
Why prove HTTP before HTTPS?
It narrows failures before certificate issuance and redirect rules add complexity.
What does the 'Point the root record' step prove?
The root domain usually needs an A record to the VPS IP. Check: dig +short example.com A returns the expected IP.
What does the 'Point www deliberately' step prove?
www can be a CNAME to the root domain or its own A record. Check: dig +short www.example.com returns a sensible answer.
What does the 'Serve HTTP first' step prove?
Certificate issuance is easier after port 80 answers correctly. Check: curl -I http://example.com returns the expected site.
What does the 'Add HTTPS last' step prove?
TLS should be configured after DNS and HTTP are already proven. Check: curl -I https://example.com returns 200 or redirect as intended.
When would you use `dig +short topicladder.com A`?
Use it to check the root a record. Expected signal: The VPS IPv4 address
Downloadable study pack
Export the same ladder as a plain Markdown note or Anki-compatible TSV. Commands and code blocks stay plain so they work in local notes.
Related paths
Study pack check passed. Notes, cards, examples, and practice tasks are meant to keep the ladder useful outside the page.
Continue learning this topic
Use this page as part of a project path, not as a one-off article. Save the note, review the cards, try the practice task, then choose the next ladder based on what your project exposes.
Study assets
Project context
- Deploy a Static Site on a VPS
- Browse Software and Linux
- Next ladder clue: Learn Nginx static roots.
Related references
Buy me a coffee for more maker ladders
TopicLadder is free to read. Support helps turn rough project paths into useful notes, cards, videos, and practice tasks.