Managing DNS programmatically has always involved workarounds. You pull records from a portal, make changes by hand, document them in a spreadsheet, then hope nothing drifts. For teams managing dozens, hundreds, or thousands of domains, that process creates real friction: deployment delays, misconfigured records, and no clean audit trail that travels with the change.
Starting today, clients can create, edit, and delete DNS records — and replace nameservers — directly through the 101domain API and MCP Server tools, without touching their control panel.
What our new DNS and nameserver endpoints cover
Four new API endpoints are now live, covering the full record management lifecycle:
POST /v1/dns/{domain_name}/records
Create up to 25 DNS records per request. Supported types: A, AAAA, CNAME, NS (subdomain delegations), MX, TXT, SRV, and CAA.
PATCH /v1/dns/{domain_name}/records
Edit existing records by ID. Only the fields you include in the request are changed.
DELETE /v1/dns/{domain_name}/records
Delete up to 25 records in a single atomic request. If any record ID is not found, no records are deleted — the operation is all-or-nothing by design.
PUT /v1/dns/{domain_name}/nameservers
Replace nameservers for a domain. Accepts 2–13 hostnames. Returns 200 if the configuration was already current, or 202 if the change is pending registry processing.
All four require the dns_write scope on your API key. Because scopes are set at key creation and cannot be added afterward, you’ll need to generate a new key if your current one doesn’t include it — that takes under a minute in Developer Settings.
Why this feature matters for teams running automated pipelines
Most teams we work with that manage large domain portfolios run into the same bottleneck: DNS changes are the one thing that still requires a human to log into a portal. A deployment script can provision infrastructure, update a load balancer, push a build — but swapping an A record or adding a Google Workspace TXT verification still breaks the automation chain.
These endpoints close that gap. Your provisioning scripts, CI/CD pipelines, and internal tools can now handle DNS changes end-to-end without a context switch to a browser. Combined with the existing read endpoints — which return full zone data including nameserver assignments — you have everything needed to build complete DNS automation workflows.
The same capabilities are available for AI agents with our MCP Server
Four new MCP Server tools mirror these endpoints for teams using AI agents with 101domain:
add-domain-dns-records-tool
Creates records from a natural language description of what you need.
edit-domain-dns-records-tool
Modifies existing records without requiring you to look up record IDs — the tool resolves them internally.
remove-domain-dns-records-tool
Removes records by description, with ID resolution handled automatically.
edit-nameservers-tool
Replaces nameservers conversationally. The tool reports back whether the change applied immediately or is pending registry processing.
In practice, this means an agent connected to your 101domain MCP Server can execute a DNS change from a plain-language instruction — “add a TXT record for Google Workspace verification to example.com” — without the user needing to know the record format or look up any IDs. The record ID friction that typically blocks AI-assisted DNS workflows is handled on the tool side.
A few things worth knowing before you start
DNS write access — both via API and MCP — applies to domains using 101domain managed nameservers or Secure Web Accelerator (SWA) powered by Cloudflare DNS nameservers. If a domain is delegated to 3rd party nameservers, the API cannot read or modify its zone data.
Recommended key scope for DNS-only agents: If you’re configuring a key specifically for DNS work, a combination of dns_read and dns_write — and nothing else — is the minimum footprint. Scopes cannot be added to a key after it’s created, so plan accordingly when generating it.
Full technical documentation — including request and response examples, status code reference, and scope requirements — is in the DNS Write Endpoints guide and the API documentation. MCP tool descriptions and connection setup are in the MCP Server Tools reference.
Ready to add DNS write access to your integration?
Generate a new API key with the dns_write scope in Developer Settings, then follow the DNS Write Endpoints guide to start managing records programmatically.