Rackspace Cloud DNS needs the tenant/account ID, username and API key for the intended account. The adapter exchanges those credentials through the identity service and uses the resulting token for DNS requests. Entering an account number from another region or customer can prevent otherwise valid credentials from reaching the correct DNS resources.
01 Collect the matching details
Obtain the account number, username and API key from the authorised Rackspace Cloud account. Confirm the Cloud DNS endpoint appropriate to the account's service catalogue and region. The default connection uses the standard US DNS API base; UK accounts may require the London DNS endpoint.
Keep the DNS API base and the Identity endpoint as separate values. The module handles the account path and token exchange. Do not paste a full one-domain URL or an expired X-Auth-Token value into the credential fields.
02 Configure Domain Nexus
- Add a server and choose Rackspace Cloud DNS.
- Enter Rackspace tenant/account ID, Rackspace username and Rackspace API key.
- Review Cloud DNS API base URL and Identity endpoint against the provider account.
- Set an appropriate SOA contact email if you do not want the zone-based default.
- Save, check the connection and inspect an owned test zone. Apply a temporary TXT change and read the result after the provider operation completes.
Common questions
Why does authentication succeed but the zone list fail?
The identity service and DNS resource endpoint are different stages. Verify the tenant ID, regional endpoint and DNS permissions associated with the authenticated account. A valid token does not prove access to a different tenant's zones.
Why should I wait for the operation result?
Provider APIs can accept a change before their final task is complete. Use the module's task and readback evidence, then query the authoritative nameserver. Do not immediately submit the same operation as a new request because the public answer has not yet changed.
When replacing an old account key, coordinate every DNS connection and other application that uses it. Preserve the working endpoint and account mapping during the credential change.