Skip to content
Skip to this exploration
All explorations

Practical self-hosting · beginner

08 · Three questions before blaming the certificate

Separate naming, routing and TLS identity.

10 min 5 sectionsv1

What you can take away

  • Diagnose a hypothetical HTTPS failure by layer.
  • Draw a request for `lesson.example.com`, an intentionally reserved example name, without making any DNS changes

Your trail through this idea

Checking saved progress…

A familiar domain shows a certificate error after a server move. The server may be healthy, yet the browser is reaching the wrong destination. DNS, routing, and TLS answer different questions.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

DNS helps locate a service. Routing and proxy configuration deliver the connection. TLS authenticates the endpoint’s name and protects the connection. A certificate does not prove that an application’s authorization rules are correct. A successful local HTTP request does not prove the public HTTPS path works.

Let’s Encrypt’s challenge documentation distinguishes HTTP-01 and DNS-01 validation. The first relies on a reachable HTTP challenge location; the second relies on a DNS TXT record. DNS automation credentials can be powerful. Choosing a challenge method changes the recovery and credential-management problem, not merely the certificate command.

Checking saved progress…

Work through the case

Original diagnostic case: an old DNS record still points at an earlier server, while the new server has a valid certificate. Reissuing the certificate on the new host cannot change the destination selected by the client. Another case: the correct proxy serves a certificate for a different name. Here, name selection or certificate configuration deserves attention.

Checking saved progress…

Make something useful

Try this

Original exercise

Draw a request for lesson.example.com, an intentionally reserved example name, without making any DNS changes. List the observation you would collect at each layer: resolved destination, responding proxy, certificate subject names, and application response. For each hypothetical failure, choose the first discriminating check. Keep real domains, addresses and DNS credentials in private operator records.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

Can a valid certificate fix a DNS record pointing at the wrong server?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

Finish with a certificate-renewal dependency list: DNS provider, challenge method, network path, credentials if any, and renewal alert. A working certificate today is not evidence that renewal will work next month.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations