LUNAROPS · OPERATIONAL UPLINK 100% UPTIME 1,247d POSTS 908 JEFF.MOON@LUNAROPS.DEV UTC --:--:--
[ OPS_LOG.STREAM ] // 22:14:08 UTC

The systems run while
the rest of the world sleeps.

Field notes on Linux, distributed systems, and the unglamorous machinery of production. Maintained from a small homelab on the quiet side of the orbit.

SCOPE · TRACKING LIVE
PHASEWAXING CRESCENT ILLUM23.4% AZ / ALT284° / 12° DIST378,221 km
POSTS · TOTAL
908
WORDS · CUMULATIVE
3,432,492
CATEGORIES
29
LAST POST
Oct 08
AVG READ TIME
19m
NEXT BUILD
on push
[ INDEX.LATEST ]

Most recent · all sections

№
DATE
SECTION
TITLE / SUMMARY
TAGS
READ
№ 907
Oct 08
AI & MACHINE LEARNING
Transformers and Attention: The Architecture Behind the Whole Field
Queries, keys, and values are three learned projections of the same input, and everything else follows from that. This covers why the scaling factor is there, what multi-head attention buys, why position has to be injected separately, and how one quadratic term shaped every optimization that came after.
#transformers #attention #neural-networks
%!d(float64=13) min
№ 906
Oct 07
DEVOPS
ACME Clients Compared: certbot, acme.sh, lego, and Caddy
Four clients implement the same protocol and produce the same certificates, so the choice is entirely about operations: how renewal is scheduled, how your service gets reloaded, where state lives, and what happens at 3am when the hook fails silently. A comparison by environment rather than by feature checklist.
#acme #certbot #letsencrypt
%!d(float64=13) min
№ 905
Oct 07
DEVOPS
Certificate Lifecycle Automation and the 47-Day Future: Renewal as a Reliability Problem
Public TLS certificates are on a schedule to 47 days, and domain validation reuse collapses to 10 days alongside it. That turns renewal from a yearly errand into a production dependency with an SLO. This is how to inventory what you have, alert on failure-to-renew rather than imminent expiry, and use ARI.
#tls #certificates #acme
%!d(float64=13) min
№ 904
Oct 07
SECURITY
Certificate Transparency: Append-Only Logs and Watching Your Own Domains
Any of 150-odd trusted CAs can issue a certificate for your domain without telling you, and before 2013 there was no way to find out. CT makes issuance publicly verifiable with Merkle trees and inclusion proofs. Here's the machinery, how to monitor your domains, and why your hostnames are now public.
#certificate-transparency #tls #pki
%!d(float64=14) min
№ 903
Oct 07
INFRASTRUCTURE
Certificates in Traefik: The Resolver Model, acme.json, and the HA Wall
Traefik issues its own certificates, which is wonderful until you need a wildcard, a custom TLS policy, or a second replica. This is the static/dynamic config split that confuses everyone, what actually lives in acme.json, how SNI picks a certificate, and the architectural wall you hit at two instances.
#traefik #acme #letsencrypt
%!d(float64=13) min
№ 902
Oct 07
NETWORKING DEEP DIVES
Debugging DNS: dig, delv, and the Resolution Path
Most DNS debugging goes wrong at the first step, because dig does not query what your application queries and +trace does not take the path your resolver takes. This is a decision tree for isolating where a wrong answer comes from, plus the traps — negative caching, EDNS fragmentation, expired signatures.
#dns #troubleshooting #dig
%!d(float64=15) min
№ 901
Oct 07
DEVOPS
DNS as Code: Zones in Git, Reviewed Diffs, and Drift You Can Actually See
DNS is often the last production system still edited by hand in a web console, with no diff, no review, and no rollback. This compares OctoDNS, DNSControl, and Terraform for managing zones declaratively, and covers the parts that actually matter: the plan/apply pipeline, drift detection, and shared zones.
#dns #infrastructure-as-code #octodns
%!d(float64=15) min
№ 900
Oct 07
NETWORKING DEEP DIVES
DNS-01 Challenges and Wildcard Certificates: Proving You Own a Zone
A wildcard certificate can only be issued through the DNS challenge, and the DNS challenge requires handing an automated renewal script a credential that can rewrite your zone. This is how DNS-01 actually works, why propagation is the hard part, and how CNAME delegation shrinks the blast radius to nothing.
#dns #acme #letsencrypt
%!d(float64=13) min
№ 899
Oct 07
NETWORKING DEEP DIVES
Dynamic DNS and DNS-Based Service Discovery: Writing Records at Runtime
Two different problems share the name "dynamic DNS": keeping a record current when an address moves, and using DNS as a service catalog. This covers RFC 2136 UPDATE with TSIG, DHCP-to-DNS integration, surviving a residential ISP, and what SRV records and Consul's DNS interface can and cannot tell a client.
#dns #rfc2136 #tsig
%!d(float64=13) min