Generate or obtain an authorised API token for the DNSPod account that manages the intended domains. Keep its numeric identifier and secret value together. Join them with one ordinary comma, with no surrounding quotation marks or extra spaces. The entire combined value is sensitive even though the identifier alone is not the secret.

Confirm which DNSPod API service your account uses. The module defaults to https://api.dnspod.com. Change that address only to the appropriate documented service for your account and the installed adapter, not to a browser dashboard URL.

1. In Domain Nexus Servers, select DNSPod.
2. Paste the combined credential into Login Token (id,token).
3. Review API Base URL and save.
4. Run the connection check. It makes a small domain-list request, so its result concerns API authentication and domain visibility.
5. Use an owned test zone to check record reads and a temporary TXT update. Confirm the returned provider record before assigning the connection to customer products.

DNSPod can return an application-level status inside an HTTP response. Preserve the actual provider message and Domain Nexus task reference when reporting a problem. A network response by itself is not proof that the requested DNS operation succeeded.

For an existing large zone, allow the discovery or read operation to complete. The adapter follows the provider's pages to build the record inventory. A partial manually copied list is a poor basis for replacing a zone because missing rows might include email or verification records.

Check that the registrar delegates to the DNSPod service assigned to this domain. Then compare the authoritative answer with the desired record and the completed task. A wrong provider account, missing permission or old delegation needs its own correction; waiting for caches does not repair those conditions.

• Discover existing DNS zones and link only verified customer ownership
• Check DNS propagation and find the source of an old answer
• Coordinate provider API quotas across web requests and background workers
• Connect Cloudflare with a scoped token and the correct account

• DNSPod: Common request parameters