DNS, SSL and email are connected to the domain but are separate services. Many outages happen because one is changed without understanding the others.
DNS is the routing layer
DNS records tell browsers and mail systems where to go. Website records commonly use A, AAAA or CNAME. Email relies on MX records and additional TXT records for authentication.
Changing nameservers can replace the entire DNS zone, so copy all existing records before switching providers.
SSL protects the connection
An SSL certificate enables HTTPS and confirms the domain identity to the browser. Certificates must cover the correct hostnames and renew before expiry.
After installation, redirect HTTP to HTTPS and check for mixed content caused by old image or script URLs.
Business email depends on more than MX
MX records direct incoming mail, while SPF, DKIM and DMARC help receiving systems verify legitimate messages. Incorrect records can cause mail to be rejected or delivered to spam.
Website contact forms also need a reliable sending method. Using the visitor address as the From address often fails modern authentication checks; use a domain or authenticated SMTP sender and set the visitor as Reply-To.
Plan changes to avoid downtime
Before moving a website or changing DNS, document current records and reduce TTL when possible. Prepare the new server and SSL first, then switch traffic.
Keep the old service running during propagation and test web and email separately.
Maintain ownership and access
The business should know who controls the domain registrar, DNS provider, hosting and email administrator. Use role-based access and secure recovery details.
Losing access to the domain account can be more serious than losing access to the website files.
Monitor the environment after changes
After a migration, upgrade or DNS change, monitor response time, error logs, storage, memory, scheduled tasks, SSL renewal, backups and email delivery. Some faults appear only after traffic increases or a scheduled process runs.
Keep the previous environment or a verified restore point available during the observation period. Recovery is much easier when the last known working state has not been removed.
Confirm ownership and access
The business should know who controls the domain, DNS, hosting account, server credentials, backup storage and business email. Avoid leaving critical assets inside an account owned only by a former developer or agency.
Use named accounts where possible, enable multi-factor authentication and keep an access register. When staff or providers change, revoke old access instead of sharing the same permanent password.
