Register librenot.es domain and configure DNS #4

Closed
opened 2026-02-25 16:05:06 +01:00 by libretech · 1 comment
Owner

Summary

Register the librenot.es domain and configure DNS records.

Tasks

  • Register librenot.es domain
  • Configure A/AAAA records for application server
  • Configure MX records if email sending is needed
  • Set up SSL/TLS certificate (Let's Encrypt)
  • Verify DNS propagation

Acceptance Criteria

  • librenot.es resolves to the correct server IP
  • HTTPS works with valid certificate
  • DNS records are documented
## Summary Register the librenot.es domain and configure DNS records. ## Tasks - [x] Register librenot.es domain - [ ] Configure A/AAAA records for application server - [ ] Configure MX records if email sending is needed - [ ] Set up SSL/TLS certificate (Let's Encrypt) - [ ] Verify DNS propagation ## Acceptance Criteria - [ ] librenot.es resolves to the correct server IP - [ ] HTTPS works with valid certificate - [ ] DNS records are documented
libretech added the phase-0 label 2026-02-25 16:05:06 +01:00
libretech added the task label 2026-02-28 09:35:45 +01:00
libretech added the infrastructure label 2026-03-02 15:45:53 +01:00
Author
Owner

Deployed at https://ln.cloud.librete.ch/ via netcup edge (caddy + INWX DNS-01 wildcard *.cloud.librete.ch). librenot.es apex registration + DNS deferred until separate decision; tracking under follow-up if needed.

  • A/AAAA: covered by *.cloud.librete.ch wildcard at INWX → 37.120.174.54
  • TLS: Let's Encrypt via INWX DNS-01, auto-renew
  • Verified: curl https://ln.cloud.librete.ch/ → 200

Closing as scoped to current netcup deployment.

Deployed at https://ln.cloud.librete.ch/ via netcup edge (caddy + INWX DNS-01 wildcard `*.cloud.librete.ch`). `librenot.es` apex registration + DNS deferred until separate decision; tracking under follow-up if needed. - A/AAAA: covered by `*.cloud.librete.ch` wildcard at INWX → 37.120.174.54 - TLS: Let's Encrypt via INWX DNS-01, auto-renew - Verified: `curl https://ln.cloud.librete.ch/` → 200 Closing as scoped to current netcup deployment.
Sign in to join this conversation.