ClouDNS DNS API

Name: ClouDNS DNS API API
Brand: ClouDNS DNS API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingapiKey13 EndpointsREST

For Agents

Manage authoritative DNS zones and records on ClouDNS — register zones, add and modify A/AAAA/MX/CNAME/TXT records, and check propagation status across nameservers.

Quickstart

Get started with ClouDNS DNS API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"add a DNS record"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ClouDNS DNS API API.

Add, modify, and delete individual DNS records inside a zone

List zones with pagination and retrieve aggregate zone statistics

Activate or deactivate DNS zones without deleting their records

Check whether a zone has fully propagated across all ClouDNS nameservers

GET STARTED

Start building with ClouDNS DNS API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ClouDNS DNS API API for, with concrete tasks.

★ Automated DNS Provisioning for New Customer Domains

Hosting providers and SaaS platforms that issue subdomains or full domains to customers can use the ClouDNS API to register a new zone and seed it with the required A, CNAME, and MX records in a single workflow. The /dns/register.json and /dns/add-record.json endpoints handle zone creation and record population, and is-updated.json confirms global propagation before the customer-facing service is announced as ready. Typical end-to-end provisioning takes under a minute including propagation checks.

Register the zone example-customer.com, add an A record for the apex pointing to 203.0.113.10, add a CNAME for www pointing to the apex, and poll is-updated.json until propagation completes

Bulk DNS Record Updates During Migrations

When migrating between hosting providers, mail providers, or CDN edges, infrastructure teams need to update many records consistently. The ClouDNS API exposes mod-record.json for in-place edits and delete-record.json plus add-record.json for full replacements, while list-zones.json and records.json provide the inventory needed to plan the change. Updates apply to the Anycast network within seconds and propagation can be tracked via update-status.json.

List all records in zone acme.com, identify every A record pointing to the legacy IP 198.51.100.5, and modify each one to point to 203.0.113.42

Scheduled Zone Propagation Monitoring

Operations teams running production DNS changes need confirmation that updates have replicated across every authoritative nameserver before declaring a change complete. The update-status.json and is-updated.json endpoints return per-nameserver propagation state and a single is-fully-updated boolean. Polling these endpoints from a CI job or monitoring system replaces manual dig checks against each ClouDNS nameserver.

After modifying a TXT record on zone acme.com, poll is-updated.json every 10 seconds for up to 2 minutes and report when the zone is fully synchronised

Agent-Driven DNS Operations via Jentic

AI agents that manage cloud infrastructure can call the ClouDNS API through Jentic to add, change, or remove DNS records as part of larger workflows such as TLS certificate validation, mail server setup, or domain handover. Jentic resolves the intent, supplies the auth-id and auth-password from its credential vault, and returns structured results so the agent can verify the change without parsing raw responses. Setup is search-load-execute rather than reading the ClouDNS HTTP API wiki.

Through Jentic, search for 'add a DNS record', load the ClouDNS add-record.json operation, and execute it to create a TXT record for ACME DNS-01 challenge validation

Key Endpoints

13 endpoints — the cloudns dns api provides programmatic management of authoritative dns zones and records hosted on the cloudns global anycast network.

METHOD

PATH

DESCRIPTION

POST

/dns/register.json

GET

/dns/list-zones.json

List DNS zones

GET

/dns/records.json

List DNS records for a zone

POST

/dns/add-record.json

Add a DNS record to a zone

POST

/dns/mod-record.json

Modify an existing DNS record

POST

/dns/delete-record.json

Delete a DNS record

GET

/dns/is-updated.json

Check whether a zone is fully propagated

POST

/dns/register.json

GET

/dns/list-zones.json

List DNS zones

GET

/dns/records.json

List DNS records for a zone

POST

/dns/add-record.json

Add a DNS record to a zone

POST

/dns/mod-record.json

Modify an existing DNS record

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ClouDNS auth-id and auth-password are stored encrypted in the Jentic vault (MAXsystem) and injected as query parameters only at execution time. The agent never sees the raw credentials, and they are not written into prompt history.

Intent-based discovery

Agents search by intent (e.g. 'add a DNS record', 'check DNS propagation') and Jentic returns the matching ClouDNS operation with its input schema, so the agent can call the right endpoint without reading the ClouDNS HTTP API wiki.

Time to first call

Direct ClouDNS integration: half a day to a day for credential handling, request signing, and response parsing across JSON and XML. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloudflare API

Cloudflare also offers authoritative DNS plus a global edge network, CDN, and security features

Choose Cloudflare when the workload also needs CDN, WAF, or edge workers; choose ClouDNS when the requirement is pure authoritative DNS hosting

Complementary

DigitalOcean API

DigitalOcean exposes droplet, networking, and DNS endpoints for compute infrastructure that pairs with ClouDNS-managed zones

Use DigitalOcean to provision the server then ClouDNS to point production DNS records at the server's public IP

Alternative

AWS API

Amazon Route 53 (via the AWS API) is an alternative authoritative DNS provider integrated with the AWS ecosystem

Choose Route 53 when the rest of the stack is in AWS; choose ClouDNS for a standalone DNS provider with a simpler pricing model

FAQs

Specific to using ClouDNS DNS API API through Jentic.

What authentication does the ClouDNS DNS API use?

The ClouDNS DNS API uses an apiKey scheme: every request must include auth-id and auth-password as query parameters. Through Jentic these credentials are stored in the Jentic vault and injected at execution time, so they never appear in the agent context or in logs.

Can I add and modify individual DNS records with the ClouDNS DNS API?

Yes. /dns/add-record.json creates a record, /dns/mod-record.json updates an existing one in place, and /dns/delete-record.json removes it. The endpoints accept the standard ClouDNS record types (A, AAAA, MX, CNAME, TXT and others) plus the zone name and record body.

How can I tell when a DNS change has propagated across all ClouDNS nameservers?

Call /dns/is-updated.json with the zone name to get a single boolean indicating full propagation, or /dns/update-status.json for per-nameserver state. Polling is-updated.json every few seconds is the standard pattern for confirming a change before downstream services start using it.

What are the rate limits for the ClouDNS DNS API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. ClouDNS publishes account-tier limits in its wiki and applies throttling at the account level, so very high volume callers should batch updates and back off if requests start to fail. For agent workloads through Jentic, retries are handled by the SDK.

How do I add a DNS record with the ClouDNS DNS API through Jentic?

Install the SDK with pip install jentic, search for 'add a DNS record', load the cloudns.net add-record.json operation, and execute it with the zone name, record type, host, and record value. Jentic supplies the auth-id and auth-password automatically and returns the structured response from /dns/add-record.json.

Does the ClouDNS DNS API support both JSON and XML responses?

Yes. The same endpoints are available with .json or .xml suffixes. The Jentic-published spec covers the .json variants since structured JSON is what agents and SDKs consume directly.