Before you start
Prepare the right information
- The school must control the domain registrar account and be able to change its nameservers.
- Review any existing website, email, verification, and third-party DNS records before changing nameservers.
Workflow
Complete the task step by step
- 1
Open Custom domain and review the current primary public URL.
- 2
Add only the root domain, without https, www, a page path, or spaces.
- 3
Confirm that required email and service records have been reviewed or contact support before delegation.
- 4
At the registrar, replace the current nameservers with ns1.softwarefordrivingschool.com and ns2.softwarefordrivingschool.com.
- 5
Wait for delegation to propagate, then return to the domain record and choose Check nameserver connection.
- 6
Make the verified and secured domain primary only after the status panel says it is ready.
- 7
Open the homepage, enrollment, booking, contact, legal, sitemap, and a published article on the custom domain before announcing it.
Expected result
What success looks like
The connecting a custom school domain 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
- The included Software for Driving School subdomain remains the fallback until a verified domain is primary.
- Dashboard, login, subscription billing, and platform administration stay on softwarefordrivingschool.com.
Important
Keep these boundaries in mind
- The included Software for Driving School subdomain remains the fallback until a verified domain is primary.
- Dashboard, login, subscription billing, and platform administration stay on softwarefordrivingschool.com.