Skip to main content
NameGrid gives you full programmatic control over the DNS records attached to your domains. You can list existing records, add new ones, update values in place, and delete records you no longer need — all through a straightforward REST API. Changes are applied automatically, even if the domain is still being provisioned.

Supported record types

NameGrid supports the following DNS record types: A, AAAA, ALIAS, CNAME, HTTPS, MX, NS, PTR, SRV, SVCB, TLS, and TXT. If you need a record type that is not listed here, contact support.

Listing records

Retrieve all DNS records for a domain with a GET request to /v1/domains/{domain}/dns.
Response
Each record object includes a unique id that you use to update or delete that record later.
When pendingFulfillment is true, the domain is still being provisioned by the registry. Any changes you make are saved immediately and will be applied automatically once provisioning completes — you don’t need to resubmit them.

Adding a record

Create a new DNS record by sending a POST request to /v1/domains/{domain}/dns. The request body supports the following fields: The example below adds a CNAME record pointing www to the root domain.
Response
Save the id returned in the response. You need it to update or delete this record in the future — there is no way to look up a record by its content alone.

Updating a record

Change an existing record by sending a PATCH request to /v1/domains/{domain}/dns/{recordId}. Include only the fields you want to change. The example below updates an A record’s IP address.
Response

Deleting a record

Remove a record permanently by sending a DELETE request to /v1/domains/{domain}/dns/{recordId}.
Response

Common DNS configurations

To direct your domain to a web server, add an A record at the root (@) pointing to your server’s IP address. Then add a CNAME for www that points back to the root domain so both yourdomain.com and www.yourdomain.com resolve correctly.Root A record
www CNAME record
An MX record tells other mail servers where to deliver email for your domain. The value field must be the hostname of your mail server. Most providers also require a priority value prepended to the hostname (e.g. 10 mail.example.com).
Check your email provider’s documentation for the exact hostname and priority values to use.
Many services (Google Workspace, GitHub, SSL certificate authorities, etc.) ask you to prove that you own a domain by adding a TXT record containing a verification token they provide.
Replace the value with the exact token string supplied by the service you are verifying with.