Before you start
Prepare the right information
- Identify whether the domain currently uses Microsoft 365, Google Workspace, cPanel mail, or another email provider.
Workflow
Complete the task step by step
- 1
Export or record every required MX, SPF, DKIM, DMARC, verification, and service record before changing nameservers.
- 2
Record any active subdomains used by portals, forms, calendars, or other vendors.
- 3
Contact support before delegation when the school relies on domain email or an unfamiliar DNS record.
- 4
After activation, verify inbound mail, outbound mail, SPF, DKIM, and DMARC with the school's email provider.
Expected result
What success looks like
The protecting school email during a nameserver change workflow is configured or understood, and the user knows the next dashboard step.
Public website impactNothing changes on the public website until an authorized user saves or publishes a setting that is designed to be public.
Troubleshooting
Common problems to check
- Nameserver delegation changes who answers DNS queries; it does not transfer an email account or recreate third-party records automatically.
- The included school subdomain continues serving the tenant website while the custom domain is being prepared.
Important
Keep these boundaries in mind
- Nameserver delegation changes who answers DNS queries; it does not transfer an email account or recreate third-party records automatically.
- The included school subdomain continues serving the tenant website while the custom domain is being prepared.