Skip to content
DNSmigrator
betaDNS betaRegistrar betaRegistrarSetup guide checked 2026-09-27

CSC Global Domain Manager

CSC API token setup: have your CSC service team enable DomainManager API v2 and issue a dedicated API key and user token with DNS and registrar rights.

On this page

CSC API token permissions

Credential type
API key and bearer token
Preview access
Zone view, domain read, nameserver read, and DS-record read
Apply access
Zone edit, nameserver modification, and DS-record add/remove
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

CSC does not publish the current role labels outside its customer documentation. Ask the API administrator to scope the user to the relevant zones and domains. Check access performs a read only.

DNSControl id

creds.json TYPE
{
  "TYPE": "CSCGLOBAL"
}

Create credentials

Have your CSC service team enable DomainManager API v2 and issue a dedicated API key and user token with DNS and registrar rights.

Access you'll grant

Preview

Zone view, domain read, nameserver read, and DS-record read

Apply

Zone edit, nameserver modification, and DS-record add/remove

CSC does not publish the current role labels outside its customer documentation. Ask the API administrator to scope the user to the relevant zones and domains. Check access performs a read only.

Before you start

  • A CSC DomainManager account managed by a CSC service team.
  • A DomainManager API administrator who can provision an API user and token.

Setup steps

0 of 5 done

  1. Request API v2 access

    Ask your CSC service team or account manager to enable DomainManager API v2 for your account. API activation is not self-service.

    Open CSC DomainManager API v2

  2. Provision a dedicated API user

    Have your DomainManager API administrator create a service user limited to the zones and registered domains DNSMigrator will manage. Include read access for previews and zone edit, nameserver modification, and DS-record management for apply.

    Preview accessZone view; domain, nameserver, and DS-record read
    Apply accessZone edit; nameserver modification; DS-record add/remove

  3. Obtain the API key

    Copy the account's API key from the CSC API administrator. This is sent in the apikey request header and is different from the user token.

  4. Generate the user token

    Generate a Bearer token for the dedicated API user and copy the full value. Tokens can stop working and then must be refreshed or regenerated in DomainManager.

  5. Enter the CSC credentials

    Paste the values into API key and Bearer token. Select OT&E (test) only when CSC issued credentials for its OT&E environment; otherwise keep Production.

Troubleshooting

CSC rejects the API key or bearer token

Confirm the key and token belong to the same environment. Refresh or regenerate the user token if it is no longer active.

CSC returns forbidden

The API user lacks a right or is not scoped to the zone/domain. Ask the DomainManager API administrator to add the specific read or modification access.

A nameserver or DS change is awaiting approval

Approve the submitted order in your CSC approval workflow. DNSMigrator cannot bypass an account approval policy.

The destination zone cannot be found

CSC zones cannot be created by this connection. Ask CSC to create the zone before applying records.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
API keyapiKeyRequiredThe DomainManager API v2 account key supplied by your CSC API administrator or service team.
Bearer tokenuserTokenRequiredThe bearer/user token generated for the dedicated API user. Paste the token itself, without the word Bearer.
EnvironmentenvironmentOptionalProduction by default. Choose OT&E only for a separate CSC test account and its OT&E credentials.

Capabilities

Create zones
No
List zones
Yes
DNSSEC
Managed in the provider console
Minimum TTL
60 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA

Caveats

  • CSC applies zone edits asynchronously and allows one pending edit per zone, so an apply waits for earlier edits to finish.
  • Only A, AAAA, CNAME, MX, NS, SRV, TXT and CAA records can be managed; zones must be created by CSC.
  • Bearer tokens expire; refresh the token in CSCDomainManager if access stops working.

Troubleshooting

CSC rejects the API key or bearer token
Confirm the key and token belong to the same environment. Refresh or regenerate the user token if it is no longer active.
CSC returns forbidden
The API user lacks a right or is not scoped to the zone/domain. Ask the DomainManager API administrator to add the specific read or modification access.
A nameserver or DS change is awaiting approval
Approve the submitted order in your CSC approval workflow. DNSMigrator cannot bypass an account approval policy.
The destination zone cannot be found
CSC zones cannot be created by this connection. Ask CSC to create the zone before applying records.

Related links

CSC Global Domain Manager migration overviewMarketing overview and provider differences.Connect a providerHow connection checks and permissions work.Cloudflare → CSCRoute 53 → CSCAzure DNS → CSCCloud DNS → CSC