Tencent Cloud DNSPod DNS Record Management

Problem

When an agent operates Tencent Cloud DNSPod directly, the failure mode is rarely missing tccli syntax. It is usually stale assumptions about API parameters, record types, TTL limits, record lines, or the OAuth flow. In high-risk changes, deleting a record, omitting RecordType / RecordLine / Value, or repeatedly changing DNS servers can interrupt resolution.

How it works

The skill narrows the scope to DNSPod resolution management: querying domains and records, creating, modifying, or deleting records, updating status and remarks, inspecting record lines, and using CreateRecordBatch / ModifyRecordBatch for batch work. Its operating principle is to treat tccli dnspod --help and the bundled references as the source of truth instead of guessing parameters. Credential setup prefers OAuth browser authorization, using tccli-oauth-helper.py --get-url and --code for non-interactive login, then verifying with a domain list query. Write operations are risk-graded: reads can run directly, while modifications and deletions require scope explanation and explicit confirmation.

Boundaries

It does not cover domain registration, renewal, transfer-in, SSL certificates, server management, or application deployment. Before changing DNS servers, compare EffectiveDNS with DnspodNsList and act only on a mismatch. Record propagation still depends on TTL and local DNS cache.