In the authenticated RcodeZero interface, open Settings, then API, and obtain the token for the authorised account. Confirm whether your service operates master zones, secondary DNS or another provider arrangement before assigning it to a package. API access to one arrangement does not establish that every zone lifecycle operation is available under your agreement.

1. Add a server with provider RcodeZero.
2. Paste the token into API Token.
3. Set API Base URL to the current service, normally https://my.rcodezero.at/api/v2.
4. Save and run the connection check. Read both its result and any notice about an old saved endpoint.
5. Assign an authorised test package, inspect the zone and make one temporary TXT change. Verify the provider record after the queued work completes.

The adapter reads the current resource-record sets and computes changes against the desired set. An incomplete manual inventory can omit mail or service-validation records that need to remain. Export or review the whole zone and use the changeset preview before a broad replacement.

Use the installed v2 workflow. If the connection rejects a response, check token validity, account access and the provider's current API service. Preserve the HTTP status and module task reference. Do not downgrade the address to silence a validation error or treat a failed read as an empty zone.

Before moving customers, confirm the authoritative nameservers and the zone's primary or secondary role. A successful API list request is only the management check. Public DNS service must also answer for the intended zone, and its registrar delegation must point to the correct service.

• Run a controlled DNS provider acceptance check before assigning customer packages
• Configure secondary DNS with an authorised transfer source
• Move managed zones to another DNS provider with a verified rollback point
• Connect DNS Made Easy with its paired API credentials
• Connect Openprovider DNS through an API-enabled contact

• RcodeZero: Documentation and workflow