Free lesson

From domain to application

From domain to application — Domain and HTTPS for your AI site. Map ownership of each layer; Trace a single request; Practice without a domain. Practical assignment: Practice: From domain to application.

Demo edition. The materials are undergoing editorial review.

Topics covered

  • Map ownership of each layer
  • Trace a single request
  • Practice without a domain

Map ownership of each layer

The registrar manages domain registration and nameserver delegation; the DNS provider answers record queries; the VPS accepts connections; Caddy routes HTTP to the application. Different companies may own these roles. Use an existing domain or local lab without purchasing or transferring registration. Record who controls each layer. If you edit a Cloudflare record while authoritative DNS still lives elsewhere, clicking Save will not change public answers. Check delegation before debugging the web server or repeatedly editing records.

Trace a single request

The educational name ai.example.com is not your domain. A client first resolves DNS, then establishes TCP/TLS and sends an HTTP request with the hostname. Caddy selects the site and forwards to an application at 127.0.0.1:3000. The model may remain entirely private rather than becoming a public upstream. Draw the route with external port 443 and loopback port 3000. HTTPS protects transport; the application must still enforce user authorization and any AI usage budget before generating responses.

Practice without a domain

Without a domain, rehearse routing through localhost and Caddy's local CA. This is not a public certificate: the client must trust that specific root. Do not disable verification with curl -k and call the result a successful trust test. A verified local CA file can be supplied explicitly through --cacert. Keep the outcome labeled local in the final report. Public DNS, certificate issuance and Cloudflare proxy remain untested rather than being represented as a deployed public site.

Practical assignment

Practice: From domain to application

Continue to learning

Course outline

  1. From domain to application
  2. DNS records and reversible changes
  3. Caddy in a local lab
  4. Public HTTPS and ACME
  5. Cloudflare proxy and two TLS connections
  6. Acceptance and rollback