Introduction
Setting up DNS for a new website requires careful planning so your site goes live without interrupting email, subdomains, or connected services. This guide explains how to review existing DNS records, add only what is needed for the new website, and protect business-critical services such as mail delivery, verification, and automation.
Issue description
The main risk during a DNS update is changing records that support email or third-party tools while pointing the domain to a new host. Common problems include website downtime, lost email delivery, broken subdomains, failed verification records, and disrupted integrations with forms, CRM, or support systems.
Signs
- The website does not load after the DNS change.
- Business email stops sending or receiving messages.
- Subdomains such as app, mail, shop, or help no longer resolve correctly.
- SPF, DKIM, or DMARC checks begin to fail.
- Forms, CRM, CDN, or automation tools stop working as expected.
Prerequisites
- Access to your DNS provider or domain registrar.
- A complete list of current DNS records.
- Details for the new website hosting provider.
- Information about any email, CDN, verification, or automation services already connected to the domain.
- A planned maintenance window for the update.
Step-by-step instructions
Step 1: Audit all existing DNS records
Review every record currently in use before making changes. Check A, AAAA, CNAME, MX, TXT, and any records for subdomains or third-party services. Export the zone file if your DNS provider supports it, or document each record manually.
Step 2: Identify records that must be preserved
Keep all mail-related and service-related records intact unless you are intentionally migrating them. In most cases, preserve MX, SPF, DKIM, and DMARC records, along with verification records for Google Workspace, Microsoft 365, Lark Suite, Cloudflare, or other connected platforms.
Step 3: Prepare the new website records
Add or update only the records required for the new website. This usually includes the A or AAAA record for the root domain and any CNAME records for www or other web subdomains. If your host provides specific DNS values, enter them exactly as provided.
Step 4: Lower TTL values before the change
If you are moving hosting, reduce the TTL on the records you plan to change before the cutover. Lower TTL values help DNS updates propagate faster and reduce the time users may see old or inconsistent results.
Step 5: Test the new host before updating production DNS
Verify the site on the new server using a temporary URL, hosts file entry, preview link, or staging domain. Confirm that pages load correctly, SSL is working, and any forms or scripts function as expected before changing live DNS.
Step 6: Update production DNS during a low-traffic window
Make the live DNS change when traffic is low. Update only the necessary website records and avoid modifying mail, verification, or automation records unless required. Double-check the hostnames, values, and record types before saving.
Step 7: Verify website, email, and connected tools
After the change, test the website from multiple networks or devices. Send and receive test emails, confirm SPF, DKIM, and DMARC behavior, and check connected tools such as forms, CRM, help desk, payment pages, and automation workflows.
Basic troubleshooting steps
- Confirm that the correct DNS record type was used for each service.
- Check for accidental edits to MX, SPF, DKIM, or DMARC records.
- Verify that subdomain records were not overwritten.
- Review TTL settings and allow time for propagation.
- Inspect the new host for SSL, firewall, or application configuration issues.
- Test any third-party integrations that rely on DNS verification or routing.
Tips and best practices
- Keep a backup of the original DNS zone before making changes.
- Change one set of records at a time so problems are easier to isolate.
- Use a staging environment whenever possible.
- Document every DNS change for future reference.
- If email is critical, avoid making DNS changes during business hours unless necessary.
Next steps
If the website is working but email or integrations are not, review the preserved records and compare them against the original DNS configuration. If you are migrating hosting, continue monitoring traffic, certificate status, and delivery logs for at least 24 to 48 hours after the update.
Additional information
For complex DNS setups involving multiple subdomains, cloud hosting, email platforms, or automation tools, consider working with an experienced implementation specialist. RKS Best can help with DNS planning, hosting migration, email deliverability, and connected system validation.
Disclaimer
DNS changes can affect website availability, email delivery, and third-party services. Always verify your configuration carefully and test in a controlled environment when possible. If you are unsure about any record, seek professional assistance before making changes to production DNS.
Comments
0 comments
Please sign in to leave a comment.