Change a domain's nameservers
Point a domain registered with Coritan at Coritan's nameservers or at another DNS provider's.
In the dashboard
A domain's nameservers decide which DNS provider answers for it. Change them when you move the domain's DNS to another provider, or back to Coritan. This page covers domains registered with Coritan; for a domain registered elsewhere, change its nameservers at that registrar.
Before you begin
Section titled Before you begin- The registration must be
active(Statuses). - Make sure the new provider already holds the domain's records. Resolvers follow the new nameservers as soon as they see them.
- To use Coritan's DNS, the domain needs a zone on Coritan that holds its records. The DNS zone row of the Registration card says Hosted here when it has one. If it does not, add the domain as an existing domain and its records first. When you switch to Coritan's nameservers without a zone, Coritan creates one on your account, with no records of yours yet.
Change the nameservers
Section titled Change the nameservers- In the dashboard, go to Domain Management, open the domain and select the Settings tab.
- In the Nameservers card, select Edit nameservers.
- Change the nameservers:
- Type over a nameserver to replace it, such as
ns1.example.net. - Select Add nameserver to add another, up to 13.
- Select the remove button beside a nameserver to take it off the list. The card keeps at least two.
- Type over a nameserver to replace it, such as
- Select Save nameservers.
To go back to Coritan's DNS, enter ns1.coritan.com to ns8.coritan.com.
Result
Section titled ResultThe dashboard confirms that the nameservers are saved, and the card lists the new set. Resolvers keep the old nameservers until their cached answers expire. Check what the registry now publishes from a terminal:
dig NS example.com +short
Once the domain points elsewhere, the records on its DNS tab no longer answer for it, and neither do Coritan's load balancers and proxied records for its names.
Troubleshooting
Section titled TroubleshootingEnter at least two nameservers.,Enter at most 13 nameservers.orFill in every nameserver, or remove the empty ones.- A domain takes 2–13 nameservers, and none of them can be empty.
Registration not found- The registration is not
active. See Statuses. Failed to update nameservers: …- The registry refused the change or did not answer. Check that each name is a working nameserver, then try again.
Domain registration is not available right now.- Coritan cannot reach a registrar at the moment, so the nameservers did not change. Try again later, and contact support if it lasts. The API answers
503with noRetry-Afterheader.
Related
Section titled RelatedWith the API
Section titled With the APISend the full list, from 2 to 13 names. Coritan lowercases them and drops a trailing dot.
curl -X PUT https://api.coritan.com/api/v1/domains/registrations/7/nameservers \
-H "Authorization: Bearer $CORITAN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"nameservers": ["ns1.example.net", "ns2.example.net"]}'
{
"message": "Nameservers updated",
"domain": "example.com",
"nameservers": ["ns1.example.net", "ns2.example.net"],
"dns_zone_id": 42,
"dns_zone_conflict": false,
"dns_zone_message": null
}
dns_zone_id names the domain's zone on Coritan, or is null when it has none. When the new list includes a Coritan nameserver and the domain has no zone, Coritan uses your zone of that name or creates one. If another account holds that zone, dns_zone_conflict is true and dns_zone_message says what to do.
API operations on this page
| Method | Path | What it does |
|---|---|---|
PUT | /api/v1/domains/registrations/{reg_id}/nameservers | Update nameservers for a domain |