Authoritative DNS comes first
When a record changes, check the authoritative server before recursive caches. It separates a publishing problem from ordinary propagation delay.
Practical notes for reliable, understandable websites.
When a record changes, check the authoritative server before recursive caches. It separates a publishing problem from ordinary propagation delay.
A small local endpoint with no database or external requests tells you whether the web process and route are alive without creating new failure modes.
Opening a socket proves very little about a route. A measured file transfer catches stalls and resets that appear after the first packets.
A concise record of listeners, certificates and validation commands makes routine maintenance safer when the original operator is unavailable.