How to Back Up DNS Records Before Changing Domain Settings

Before changing domain settings, back up current nameservers and all DNS records, including A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, CAA, SRV, subdomains, redirects, verification records, and DNSSEC settings. Save an export, screenshots, or a spreadsheet so records can be restored if website, email, SSL, CDN, or app services stop working.

Who This Guide Is For
This guide is for:
· Users changing nameservers
· Users transferring domains to NiceNIC
· Businesses relying on website and email continuity 
· Agencies and hosting providers managing DNS
· Users enabling or disabling DNSSEC

Before You Start
Before you start, prepare:
· Access to current DNS provider
· Current nameservers
· Registrar account access
· Hosting and email provider details
· DNSSEC status
· Safe storage for backup
· Permission from owner or client

Step-by-Step Instructions
Step 1: Identify Where DNS Is Hosted
Check nameservers to locate the active DNS provider.
· Registrar DNS
· Hosting DNS
· CDN DNS
· Third-party DNS
· Private DNS
Step 2: Record Nameservers
Save all current nameserver hostnames and provider notes.
· Nameserver 1 and 2
· Private nameservers and glue if used
Step 3: Export DNS Zone If Available
Use provider export if possible. If not, use screenshots and a spreadsheet.
· Save date, provider, and domain name
Step 4: Back Up Website Records
Record A, AAAA, CNAME, root, www, subdomain, CDN, app, and redirect records.
· Identify live website records
Step 5: Back Up Email Records
Record MX, SPF, DKIM, DMARC, autodiscover, mail subdomain, and provider verification records.
· MX records are priority for receiving email
Step 6: Back Up Verification Records
Save TXT and CNAME values for Google, Microsoft, SSL, CDN, website builders, SaaS, and security tools.
· Do not delete unknown TXT records
Step 7: Back Up Security Records
Record CAA, DNSSEC DS, DNSKEY details, MTA-STS, BIMI, or TLSA if used.
· Review DNSSEC carefully
Step 8: Record TTL Values
Save cache times for important records.
· TTL helps understand propagation timing
Step 9: Create a DNS Backup Spreadsheet
Use columns for type, host, value, priority, TTL, purpose, and notes.
· Useful for agencies and resellers
Step 10: Verify After Change
Test website, email, SSL, subdomains, CDN, redirects, and DNSSEC after making changes.
· Use backup to restore if needed

Troubleshooting
Website Stopped Working
Possible reasons:
· A or CNAME missing
· Nameserver changed before records copied
· DNSSEC mismatch
What to do:
· Restore website records
· Check nameservers
· Check hosting
Email Stopped Receiving
Possible reasons:
· MX missing
· SPF/DKIM/DMARC missing
· Wrong DNS provider
What to do:
· Restore MX and TXT records
· Check email provider
SSL Validation Fails
Possible reasons:
· CAA too restrictive
· TXT/CNAME validation missing
What to do:
· Restore validation records
· Check SSL provider instructions

Common Mistakes
Mistake 1: Changing nameservers before copying records
Review this item before making changes or opening a support ticket.
Mistake 2: Backing up only A records
Review this item before making changes or opening a support ticket.
Mistake 3: Forgetting MX records
Review this item before making changes or opening a support ticket.
Mistake 4: Ignoring SPF/DKIM/DMARC
Review this item before making changes or opening a support ticket.
Mistake 5: Deleting unknown TXT records
Review this item before making changes or opening a support ticket.
Mistake 6: Ignoring DNSSEC
Review this item before making changes or opening a support ticket.
Mistake 7: Not recording TTL
Review this item before making changes or opening a support ticket.
Mistake 8: Using screenshots only for complex zones
Review this item before making changes or opening a support ticket.
Mistake 9: Not testing after changes
Review this item before making changes or opening a support ticket.
Mistake 10: Making too many changes at once
Review this item before making changes or opening a support ticket.

FAQ
1. What DNS records should I back up?
Back up nameservers, A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, CAA, SRV, verification, CDN, and DNSSEC records.
2. Do I need a backup before transfer?
Yes, especially if old registrar DNS may stop after transfer.
3. Do I need backup before nameserver change?
Yes. New DNS provider must have the same required records.
4. What are MX records?
They tell mail servers where to deliver email.
5. What is DNSSEC?
A security extension that helps validate DNS responses.
6. Can DNSSEC break my domain?
Misconfigured DS records can cause resolution failure.
7. Where should I store backup?
Use secure, access-controlled storage.
8. Should I delete old records?
Only after confirming they are no longer needed.