> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/guides-and-examples/domains-and-dns/external-dns.md).

# DNS and nameservers

How to set up external DNS services to work with Release

## Select a domain to use with Release

Before you create a domain in Release, take a moment to decide whether you'll use an entire domain (in other words, all subdomains on a domain) for Release, or a single subdomain of your domain.

### When to use an entire domain name

If you do not yet have a domain name, we recommend registering a new domain through your cloud provider.

Using a domain name dedicated to Release enables launching your live environments on Release and is recommended for applications that will use permanent environments, not only ephemeral environments.

For example, you could launch a permanent environment on `www.example.com`.

### When to use a single subdomain

If you already use an external DNS server for your domain or your domain registrar does not support setting custom nameservers at domain-level (such as Cloudflare Registrar), we recommend using a subdomain for your Release applications.

This way, you can delegate DNS for the subdomain only to Release, while keeping full control over the rest of your domain with your current provider.

For example, if you choose to use `release.example.com` for your Release environments, you still have the option to use `www.example.com` and `api.example.com` for services outside Release.

Your Release environments will have domains that are one level down from your chosen subdomain, for instance, `api-23r4wm-appname.release.example.com`.

## How to get nameservers from Release

When you [create a domain](/guides-and-examples/domains-and-dns/managing-your-domains.md#create-a-domain) in Release, we automatically create a DNS zone for your domain at your cloud provider. We use Route53 on AWS or Cloud DNS on GCP.

After creating the DNS zone, Release displays the nameservers your domain or subdomain should use.

## How to configure your domain or subdomain to point to Release

Take note of the nameservers provided by Release, then follow one of the guides below to point your domain or subdomain to the Release nameservers:

* [Configure GoDaddy](/guides-and-examples/domains-and-dns/external-dns/godaddy.md)
* [Configure Namecheap](/guides-and-examples/domains-and-dns/external-dns/namecheap.md)
* [Configure Cloudflare](/guides-and-examples/domains-and-dns/external-dns/cloudflare.md) (subdomain only)
* [Other DNS hosts](/guides-and-examples/domains-and-dns/external-dns/generic-dns.md) (subdomain only)

## Be prepared to wait for propagation

Domain changes sometimes take up to a day or two to propagate. This is due to how DNS resolvers cache records. To check the status of your domain's DNS propagation, use a tool such as [DNS Propagation Checker](https://www.whatsmydns.net/) or [DNSMap](https://dnsmap.io/).

## Verify your domain in Release

Once the DNS change has propagated to most of the internet, you can [verify your domain](/guides-and-examples/domains-and-dns/managing-your-domains.md#verify-a-domain) in Release and start using it for new environments.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/guides-and-examples/domains-and-dns/external-dns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.