← Dns / dns / nameservers

Nameserver options

Refer to the following sections to learn about different Cloudflare nameserver options. The availability of these options depends on your plan. Also, if you acquired your domain from Cloudflare Registrar, your domain already uses and must remain on Cloudflare nameservers.

When you add a domain on a primary (full) or secondary DNS setup, Cloudflare automatically assigns your nameservers.

The default assignment method is to use standard nameservers and favor consistent nameserver names across all zones within an account. Nonetheless, in case there are conflicts, you may get different nameserver names, even for domains that are within the same account.

The level of consistency you can expect when adding new zones depends on the configured nameserver type.

• For standard nameservers, since a conflict can be caused by anyone adding the same zone to any other Cloudflare account, the likelihood of your new zone being assigned different nameserver names than your previously existing zones is higher.

• If you use account custom nameservers, the only conflict would be between a parent and a child zone, which makes consistent assignment across new zones more likely.

• With tenant custom nameservers or Foundation DNS advanced nameservers, there can still be conflicts caused by two zones with the same name being added to different accounts, but, since access to these features is more restricted, the likelihood of your new zone being assigned different nameserver names than your previously existing zones is lower.

If you have an Enterprise account, you also have the option to configure your own DNS zone defaults and change how Cloudflare handles nameserver assignment when you add a new zone to your account:

• Standard nameservers randomized: instead of attempting consistency, Cloudflare assigns random pairs of nameserver names every time you add a new domain to your account.
• Advanced nameservers: Cloudflare uses the same method as the default - trying to keep nameserver names consistent for different zones within an account - but uses the specific Foundation DNS nameservers.
• Account custom nameservers: Cloudflare automatically assigns a set of account custom nameservers that you have previously configured for your account. In this method, Set 1 will be attempted first and, in case of any conflicts, Cloudflare will cycle through the other nameserver sets, in ascending order.

Multi-provider DNS is an optional setting for zones using primary setup (full) and is an enforced default behavior for zones using secondary setup.

When you enable multi-provider DNS on a primary zone:

• Cloudflare will no longer ignore NS records created on the zone apex, as in the example below.

  Type	Name	Nameserver
  NS	@	ns1.external.com

This means that responses to DNS queries made to the zone apex and requesting NS records will contain both Cloudflare's and your other DNS providers' nameservers.

• Cloudflare will activate a primary zone (full setup) even if its nameservers listed at the registrar include nameservers from other DNS providers.

For both Cloudflare nameservers (standard or advanced) and custom nameservers, the NS record time-to-live (TTL) is controlled by the specific setting on the DNS Records page, under DNS record options.

The default TTL is 24 hours (or 86,400 seconds), but you have the option to lower this value depending on your needs. For example, shorter TTLs can be useful when you are changing nameservers or migrating a zone. Accepted values range from 30 to 86,400 seconds.

This setting can also be configured as a DNS zone default, meaning new zones created in your account will automatically start with the value you define.