For the complete documentation index, see llms-docs.txt or the site index llms.txt. Full docs corpus: llms-full-docs.txt. Prefer the markdown version of this page at /docs/guides/connect-domain/after/change-dns.md. Product capabilities: skill.md. Docs MCP: /docs/mcp. Site MCP: /mcp.
Change DNS later
Move your domain to a new DNS host without breaking Reloop mail authentication.
Safe migration checklist
Export current records
From the old DNS host (or Reloop dashboard), note SPF, DKIM, DMARC, MX, and tracking values.
Create the zone on the new host
Add the domain/zone at Cloudflare, Route 53, etc., and recreate all important records (website + mail), including Reloop’s.
Lower TTL beforehand (optional)
A day before, set TTL to 300s on old NS-related records if your registrar allows.
Switch nameservers at the registrar
Point NS to the new host. Keep the old zone until dig shows the new NS everywhere.
Re-verify in Reloop
After NS propagate, open the domain → Verify. Auto populate may appear if the new host supports Reloop’s Domain Connect template.
Avoid
- Deleting Reloop records on the old host before the new host is live
- Switching NS without recreating MX if you still need inbound mail
Related
Was this page helpful?
- Need help? Contact Support.
- Chat with Reloop developers on Discord.
- Check out our changelog.
- Questions? Contact Sales.
- LLM? Read llms.txt.