Technical notes
Notes on small-service operations.
Short references for maintenance work, DNS changes, backup checks, and incident follow-up.
Reference notes
Each note is written to be useful before work starts, not only after something has gone wrong.
Preparing a low-risk maintenance window
How to define impact, rollback conditions, and verification before a change begins.
What to check after a DNS change
A short list for records, TTLs, certificate coverage, and public resolution checks.
Keeping backup reviews small
Backup reviews work best when they confirm restore paths, not just file counts.
Simple uptime checks for small sites
Start with public pages, certificates, and a few critical paths before adding tooling.
Reading certificate expiry signals
What to watch before a certificate becomes urgent work.
When to write an incident note
A short note is useful when an issue affected users or changed future maintenance.
A practical rollback checklist
Define who decides, when to revert, and what to check after rollback.
Separating routine work from urgent work
Clear queues reduce mistakes when routine tasks and incidents overlap.
Small DNS habits that reduce surprises
Keep record history, TTL notes, and verification commands close to the change.
Reviewing public pages after updates
Check status codes, static assets, mobile layout, and page titles after deployment.