get_domain_dns
Re-fetch the DNS records for a domain you already registered.
›Pull the DNS records for our mail.acme.com domain again so I can send them to the client.
What it does
The same record set `create_domain` returned, fetched again by domain ID. This exists because DNS setup is rarely finished in one sitting — the person who registered the domain in Raechly is often not the person with access to the zone file.
It is read-only and safe to call repeatedly, which makes it the natural tool to reach for when you are handing setup to a colleague or a client. Ask your assistant to re-print the records and paste them into a ticket.
It is also the right tool for auditing a domain that verified months ago. DNS drifts: a zone gets migrated, a record gets tidied away by someone who did not recognise it, a registrar transfer drops entries silently. Comparing what should be published against what is live catches that before deliverability does.
Parameters
| Name | Type | Notes |
|---|---|---|
| domain_id * | string | From `list_domains`. |
* required · Maps to GET /api/domains/:id/dns
What comes back
The `dns_records[]` array for that domain.
The thing people get wrong
Re-fetching does not re-check verification. It only prints what should be published — call `check_domain` to find out whether it actually was.
Use it with
More domains tools
See all 22 tools and the connection string on the MCP server page.