How to plan DNS TTLs before a migration or cutover
Lower DNS TTLs before a cutover so caches expire fast, then raise them after. A step by step plan, with the limits of what TTL can and cannot control.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Lower DNS TTLs before a cutover so caches expire fast, then raise them after. A step by step plan, with the limits of what TTL can and cannot control.
Recursive resolvers look names up for clients, authoritative servers hold the zone data. How the two roles work and where each can fail or be attacked.
Allow-listing a domain does not stop DNS rebinding. Resolve, check every address, and connect only to the validated IP. Here is the pattern to follow.
Resolvers cache 'does not exist' answers too. Learn how the SOA value sets that delay, why a new record can stay invisible, and how to avoid it.
How a parent zone hands authority to a child with NS records, why glue records are needed, and why every zone should live on two name servers.
How DMARC treats subdomains: the sp tag for existing ones, the new np tag for non-existent ones, and the inheritance rules that decide which policy applies.
A staged DMARC rollout: start at p=none with reports, find every sender, move to quarantine, then reject. With timing guidance from RFC 9989.
RFC 9989 (May 2026) makes DMARC a Standards Track document and obsoletes RFC 7489. See what changed: DNS tree walk, t and np tags, and pct removed.
RFC 9989 drops the DMARC pct tag for gradual enforcement and adds t=y for testing. Learn why pct was removed and how to phase in a stricter policy.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.