TopicLadder
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.

Topic goal to ladder route

Know the destination, then climb the route.

A topic is the maker goal. A ladder is the route from what you understand now to one visible proof you can build, sketch, test, or explain. This one ties back to Deploy a Static Site on a VPS.

Start point

Name what you already understand before the build gets bigger.

Topic goal

Connect a domain to a VPS without guessing whether the problem is DNS, Nginx, or TLS.

Ladder route

Read the short lesson, watch one source tutorial, sketch the idea, check the math, then practice.

Project proof

Write the sequence you would use to connect a new domain to an existing VPS, including the command that proves each step.

Ladder steps

Each step should prove one idea before the project asks for the next one.

1
Point the root recordThe root domain usually needs an A record to the VPS IP. dig +short example.com A returns the expected IP.
2
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.
3
Serve HTTP firstCertificate issuance is easier after port 80 answers correctly. curl -I http://example.com returns the expected site.
4
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

Project signal

dig +short topicladder.com A

Expected signal: The VPS IPv4 address

Check the www answer

Project signal

dig +short www.topicladder.com

Expected signal: A CNAME or resolved IP

Verify public HTTP

Project signal

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 path

  • 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 lesson 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 lesson useful outside the page.

Connected routes

Use these links like a project map: what helps before this, what this unlocks, and where it fits.

What this unlocks

  • Learn Nginx static roots.
  • Learn release symlinks.
  • Learn Search Console setup when the site is ready.

Text lesson and video notes

This page works as a text lesson first. If you later watch a matching tutorial, use the notes pattern here to capture the build decision, timestamps, warnings, and the next practical task instead of saving a raw link.

Attach a video note

Save useful workshop or tutorial videos into an Obsidian note with timestamps, source links, and what each segment proves. The site does not need the video to be useful.

Turn a video into notes and cards

Review and practice

Download the cards, then finish the practice task before adding more links to your project notebook.

Open practice tasks

Source video for this ladder

Use the video as source material for notes, cards, and practice. The written ladder still works without playback.

Use the source as a companion, not as a replacement for the written ladder.

Suggest a better source video

If another tutorial explains this topic more clearly, send the title and YouTube URL. Suggestions should help the ladder, not replace it.

Suggestions are reviewed before they appear.

Topic: DNS Records and SSL for Makers

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 lesson based on what your project exposes.

Share this maker lesson

Send the context, not just a snippet.

Use the page so the lesson, source videos, notes, cards, and practice task stay attached.

Buy me a cup of coffee

TopicLadder is free to read. Coffee support helps turn rough maker ladders into clearer project paths, notes, cards, and practice labs.

Last reviewed: July 5, 2026. TopicLadder pages are curated for practical learning and may be updated as examples improve.