Changing domain means clearing the old one properly
An institution's custom domain can be removed. Where one is configured, its delivery setup is torn down and the cached copies are invalidated first, and only then is every trace of the domain cleared from the record. A new domain set up afterwards therefore starts from a clean record, with nothing left over to get in its way.
How it is done today
Changing domains without clearing the old one properly leaves it half configured. The old address works some of the time, setting the new one up gets stuck, and there is no obvious place to look for what went wrong.
How it works
- 1
Open the domain settings
The domain section of the institution's settings shows which domain is configured at the moment.
- 2
Take the remove action
Remove it from beside the configured domain. The page reports while the removal is running rather than looking frozen.
- 3
The delivery setup is torn down
Before the record is cleared, the domain's delivery setup is torn down and its cached copies are invalidated.
- 4
The record is cleared in full
The domain name, its verified state and its connection details all go together, so nothing is left in a half state.
What it looks like
Who uses it
- Used by:
- Admins
- Institution types:
- Coaching centres
- Schools
- Colleges
- Online teaching platforms
Plan availability
- CustomNegotiated
Frequently asked questions
Can a new domain be set up afterwards?
Yes. Because the old details are cleared completely, the new domain starts from a clean record with nothing left over to get in its way.
What if no delivery setup exists?
The teardown step is skipped and the record is still cleared, so removing a domain never gets stuck waiting on that step.
Who can remove a domain?
An institution admin. Whether the caller really is one is checked as the request arrives, before anything is torn down.