Join us at JAMstack Conf San Francisco, October 16-18. Register today

Managed DNS

This feature is in beta.

Netlify offers the option to handle DNS management for you. This enables advanced subdomain automation and deployment features, and ensures that your site uses our CDN for the root domain as well as subdomains like www.

General steps:

  1. Verify the domain. The domain can be managed through an external registrar or registered with Netlify during the verification step.
  2. Create a DNS zone for your domain.
  3. Add DNS records to your zone.
  4. Point your domain at the name servers assigned to your DNS zone, if the domain is registered from an external registrar.

Adding Domains

You can add domains to Netlify DNS that you own through external domain registrars, or register available domains with Netlify. Go to your team’s Domains page and select Add or register domain. Enter the domain you wish to register or add and click Verify.

If the domain is unowned, you are presented with the price and ability to register the domain and have it added to the current team’s Domains list fully configured to use Netlify DNS. The payment method on file for the team will be used, or you can add a payment method if unset. Click Register domain now to register the domain.

If the entered domain is registered through an external registrar (or already owned by someone else), you will be asked to confirm that you are the owner of the domain. If you are the owner, click Yes, add domain to create a Netlify DNS zone for the domain.

Adding DNS records

Netlify DNS supports the following types of records:

  • A: Address record, which is used to map host names to their IPv4 address.
  • AAAA: IPv6 Address record, which is used to map host names to their IPv6 address.
  • ALIAS: A pseudo-record that works like a CNAME but can be safely used at the Zone Apex because it always resolves to A (or AAAA) record(s).
  • CAA: Certificate Authority (CA) Authorization, which is used to specify which CAs are allowed to create certificates for a domain.
  • CNAME: Canonical name record, which is used to specify alias names.
  • MX: Mail exchange record, which is used in routing requests to mail servers.
  • NS: Name server record, which delegates a DNS zone to an authoritative server.
  • SPF: Sender Policy Framework record, a deprecated record type formerly used in e-mail validation systems (use a TXT record instead).
  • SRV: Service locator record, which is used by some voice over IP, instant messaging protocols, and other applications.
  • TXT: Text record, which can contain arbitrary text and can also be used to define machine-readable data, such as security or abuse prevention information.

To add a new record, go to the DNS records panel on your Domain’s DNS zone page, and select New record.

Choose the type of record to create from the dropdown menu and fill in the remaining options. The fields you need to fill out will depend on the type of record you select.

Select Save to create the record and make the changes live.

Remember, it may take up to a few hours for record changes to propagate.

Note that you can host records for other services (e.g. your mail provider, your backend API, etc) with us as long as you host at least one website with us whose hostnames is within the domain.

Directing DNS traffic to Netlify

The final step to making your DNS records live is to update your domain registrar with the nameservers that will be authoritative for your domain. Note, if you registered the domain through Netlify, you can skip this step as it is already configured to use Netlify DNS.

The process for changing your domain’s nameservers varies from registrar to registrar. Check your domain registrar’s documentation for updating nameservers. For your convenience, we’ve gathered links to instructions for popular registrars Hover and GoDaddy.

To start directing your DNS traffic to Netlify:

  • Navigate to your Domain’s DNS zone page on Netlify, and make note of the four nameservers listed in the Nameservers panel.

  • Log in to the account you have with your domain registrar and find their instructions for updating nameservers.

  • Replace the nameservers with the nameservers for your Netlify DNS zone.

It may take up to a day for the changes to propagate to the public internet.

Dedicated secondary DNS

This feature may not be available on all plans.

Netlify’s dedicated DNS network is separately provisioned from our main DNS network, providing a DNS redundancy option. For teams using our dedicated DNS network, all DNS traffic for managed domains is distributed across both DNS networks. In the event of a volumetric attack such as a Distributed Denial of Service (DDoS), the secondary network provides a physically and logically separate failover for domain name resolution.

If you would like to increase your sites’ resiliency by adding Netlify’s dedicated DNS network to a new or existing team, please contact us for more details.

IPv6 traffic

IPv6 is a new version of the IP protocol that allows your site to reach areas of the world where connectivity via IPv4 is not possible due to the lack of IP addresses. For now, IPv6 is not enabled by default on all Netlify sites, if you use Netlify’s Managed DNS you need to enable it explicitly in your Domains dashboard.

After creating a DNS Zone, you’ll be able to enable IPv6 traffic for your domain by clicking the Enable IPv6 button on the zone header:

After IPv6 is enabled for your domain, your main domain and all the branch subdomains that you create will use IPv6, as well as IPv4.

Troubleshooting DNS configuration

The dig command line tool is the best tool for quickly diagnosing and understanding DNS responses. It is built into Linux and Mac, but can also be installed on Windows.

NS1 –the DNS provider backing Netlify DNS– has a great series of articles on using DIG to test and troubleshoot your DNS configuration.

Domain transfer

You can transfer domains and DNS zones between your Netlify teams at any time.

To transfer a domain from Netlify to a different registrar, you must wait 60 days after the registration to initiate the transfer as per ICANN regulations.

Notice something is incorrect or outdated?

First off, great catch! We appreciate your discovery and want to ensure it gets addressed immediately. Please let us know here.

Want to have a conversation?

Visit the Netlify Community to discuss ideas and questions with your fellow Netlify users.

Want to get started quick?