In the DigitalOcean control panel, open Account, then API, and generate a personal access token. Give it a name identifying this Domain Nexus installation. Choose an expiration you can manage operationally and select the domain scopes required for reading, creating, updating and deleting DNS resources. DigitalOcean requires the associated read permission when granting domain write actions.

Save the secret when displayed and record its expiration. A read-only token is suitable for inspection, but cannot support a customer record editor. If you later need different custom scopes, issue a replacement token with the intended grants and rotate the integration deliberately.

1. Add a Domain Nexus server and choose DigitalOcean.
2. Paste the provider token into API Token.
3. Review Default Zone IP. When supplied, it is passed during new-zone creation. Use a real intended service address, not a temporary workstation address.
4. Save, perform the connection check and assign a test package.
5. Create an authorised test zone or adopt an existing owned one. Add a temporary TXT record, inspect the completed task and read the provider record back.

Read permission and write permission are separate. Check the token's domain scopes, its team membership and its expiration. Confirm that the domain is in the account visible to that token. Repeatedly recreating the zone will not repair an access problem.

No. The provider DNS zone and the domain registration are separate resources. Set the registrar's nameservers to the authoritative service assigned to the zone after its records are ready. Until that delegation is in place, public queries may continue to use the old DNS provider.

• Run a controlled DNS provider acceptance check before assigning customer packages
• Rotate a DNS provider credential across all connections that use it
• Choose hosting nameservers or DNS management for your domain
• Connect DNS Made Easy with its paired API credentials

• DigitalOcean: Create a personal access token
• DigitalOcean: Domain API