A mail gateway change can affect MX routing, SPF authorization, DKIM signing, and DMARC alignment. Checks to make Map inbound and outbound paths, identify all approved senders and selectors, and plan MX and authentication changes with the provider. Test delivery and headers using controlled accounts before removing the old gateway records. When to get...
Changing MX priorities can alter failover behavior or route mail to a server that is not ready to accept it. Checks to make Confirm each target is active, correctly configured, and intended as primary or fallback. Review TTL and provider guidance, validate TLS and mailbox handling, and test controlled inbound delivery before making priority changes....
A CDN cutover changes proxy behavior, origin requests, TLS termination, cache rules, and possibly DNS validation paths. Checks to make Inventory hostnames and DNS records, confirm the CDN can reach the origin, verify certificates and cache bypass rules, and test dynamic and authenticated routes. Plan TTL and rollback, then monitor origin load and...
A registrar transfer should not disrupt DNS if nameserver delegation remains intact, but access and renewal settings can change. Checks to make Record current nameservers and export the authoritative zone, confirm transfer lock and renewal status, and ensure DNS account ownership is independent of the registrar where possible. Verify delegation after...
A web server move can overlook subdomains, certificate validation records, mail services, and external integrations in the same zone. Checks to make Export and categorize current records, identify owners and destinations, and test the new server with the intended hostname. Plan TTL and rollback, preserve non-web records, and verify each important...
An old subdomain may still serve downloads, API callbacks, certificate validation, or email-related verification. Checks to make Check authoritative records, access logs, certificates, integrations, and business owners. Confirm no active dependencies, prepare redirects or replacements where needed, and monitor for residual requests before removing the...
Messages may work between coworkers while outside senders receive bounces or see no delivery. Internal routing can bypass public DNS, so an incorrect MX target, stale nameserver data, or a mail gateway rule may affect only external delivery. What to check Review the domain’s authoritative nameservers and public MX records, test each advertised mail...
After a DNS change, different networks can reach different destinations because of resolver caching, multiple authoritative nameservers, split DNS, IPv4 and IPv6 differences, or a local hosts-file override. Seeing the new site once does not prove every resolver is using the same answer. What to check Query the authoritative nameservers and compare A,...