Why this matters
A bad DNS change can take the whole website or email system offline for hours. Planned updates prevent outages.
Step-by-step instructions
1
Export current records
Most DNS hosts allow a zone file export - keep a backup.
Screenshot placeholder - step 1
2
Lower TTL 24 hours before change
Set TTL to 300 so updates propagate fast.
Screenshot placeholder - step 2
3
Make the change
Edit or add the specific record. Double-check syntax.
Screenshot placeholder - step 3
4
Save and test
Use dnschecker.org to confirm propagation.
Screenshot placeholder - step 4
5
Restore TTL to 3600+
After stability is confirmed, raise TTL.
Screenshot placeholder - step 5
Pro tips
- Always back up before editing.
- Make one change at a time.
- Schedule outside business hours where possible.
Common mistakes
- Deleting MX records and killing email.
- Editing apex records without ALIAS support.
- Raising TTL before verifying the change.
What happens next
DNS is updated safely with no downtime.