Recent searches

in

Configure CloudCannon DNS

Last modified: November 12th, 2026

On this page

Permissions required

Members of the Owners, Developers, and Partner Default Permission Groups, or Custom Permission Groups with the base-domain:settings:dns:read and base-domain:settings:dns:write permissions, can view and change the DNS of a Base Domain.

CloudCannon DNS allows you to manage your DNS Records within CloudCannon for each Custom Domain connected to your Organization. CloudCannon adds the records that point your Base Domain and its Subdomains at CloudCannon, and the TXT Records for your SSL Certificates, for you once your nameservers point at CloudCannon DNS.

Before we begin, this article assumes you have connected a Custom Domain to your Organization.

Enable CloudCannon DNS#

CloudCannon DNS is the default DNS Provider when you connect a Custom Domain. If your domain uses External DNS, you can switch it to CloudCannon DNS on the Details section of the Domain Settings tab. Switching needs the base-domain:settings:details:read permission to open the Details section, as well as the base-domain:settings:dns:write permission.

Updating your DNS Provider can cause downtime for anything connected to your domain, such as your website or custom email address. Please make sure you have a copy of your existing DNS Records before you change providers.

If you need help updating your DNS, please contact our friendly support team. Include the Custom Domain, your current DNS Provider, and a copy of your existing DNS Records.

To switch to CloudCannon DNS:

  1. Log in to CloudCannon.
  2. Select the Organization your Custom Domain is connected to.
  3. Click the Custom Domains link in the App Sidebar. CloudCannon will open the Domains Browser.
  4. Select the domain for which you want to configure DNS by clicking the Card for the domain. CloudCannon will open the Summary tab of the Domain page.
  5. Click the Domain Settings tab. CloudCannon will open the Details section.
  6. Under DNS Provider, select the CloudCannon DNS option. CloudCannon will label the provider you are switching from (current) and list What happens when you switch.
  7. Click the Switch to CloudCannon DNS button.

CloudCannon will create a DNS zone for your domain and add the records CloudCannon needs.

Nothing changes for visitors until you change the nameservers at your domain registrar. Before you change them, add your other DNS Records, such as MX Records for email and TXT Records for site verification, on the DNS tab.

A screenshot of the Details section on the Domain Settings tab shows CloudCannon DNS selected under DNS Provider, External DNS marked (current), and the What happens when you switch steps.
The Details section on the Domain Settings tab

You can also open the Details section from the DNS tab, by clicking the change the DNS Provider link below the External DNS nameservers heading at the top of the tab.

Move from the legacy CloudCannon DNS#

Some older Custom Domains use the legacy CloudCannon DNS, where you can't add or change DNS Records. Moving your domain to the new CloudCannon DNS creates a DNS zone with a copy of its current records, where you can add and edit them, and nothing changes for visitors until you update the nameservers at your domain registrar. For the steps, please read our documentation on migrating from the legacy CloudCannon DNS.

Point your domain at CloudCannon DNS#

Once you enable CloudCannon DNS, you need to replace the nameservers at your domain registrar with CloudCannon's nameservers. Until you do, a setup guide at the top of the Summary tab of your Domain page walks you through each step. The Custom Domain page under Site Settings shows the same guide for any Site on the domain, and notes that the Site stays on its Testing Domain until your domain goes live. The DNS tab shows the same guide below its CloudCannon DNS heading, a Configure CloudCannon DNS link, and a sentence that says how CloudCannon DNS answers for your domain, ending in a change the DNS Provider link.

A screenshot of the Custom Domain page under Site Settings for Careers site shows that Careers site goes live at https://careers.example.org/ once careers.example.org points at CloudCannon, and the Point example.org at CloudCannon DNS setup guide, which notes that Careers site stays on careers-site.cloudvent.net until then, with the Update your nameservers step in progress and the 1. Copy your existing DNS Records step with an Open the DNS tab button.
The setup guide on the Custom Domain page

The setup guide shows a three-step tracker (Update your nameservers, Nameservers match, and CloudCannon DNS configured) and a heading for the step you are on. Once you click the I've updated my nameservers button, the first step reads You updated your nameservers. While CloudCannon checks your nameservers, the second step reads Checking nameservers, and if CloudCannon can't detect them, Nameservers do not match:

  • Getting [Base Domain] ready — CloudCannon is creating the DNS zone for your domain. Your nameservers show once the zone is ready, usually in a moment.
  • CloudCannon could not create a DNS zone for [Base Domain] — CloudCannon couldn't create the DNS zone, and shows Cloudflare's reason under Error reason. Click the Retry zone creation button to try again.
  • Point [Base Domain] at CloudCannon DNS — Update the nameservers at your domain registrar.
  • Waiting for CloudCannon nameservers on [Base Domain] — Your registrar is handing your domain over to CloudCannon DNS.
  • [Base Domain]'s nameservers do not match the CloudCannon nameservers — CloudCannon still can't see your new nameservers 48 hours after you clicked the I've updated my nameservers button.
  • [Base Domain]'s nameservers no longer point at CloudCannon DNS — Your domain was live on CloudCannon DNS, but its nameservers no longer point at CloudCannon.

If the zone still can't be created after you retry, contact our friendly support team. Include your Base Domain and the reason Cloudflare gave in the setup guide.

A screenshot of the setup guide on the Summary tab shows the Point example.org at CloudCannon DNS heading, the Update your nameservers step in progress, the 1. Copy your existing DNS Records step with an Open the DNS tab button, and the 2. Update your nameservers table with each required nameserver marked Update needed.
The setup guide while you update your nameservers

Add your existing records

Unless you moved from the legacy CloudCannon DNS, CloudCannon doesn't copy records from your current DNS Provider. Records at your current DNS Provider stop working once you switch nameservers, so add them to CloudCannon DNS first. These usually include MX Records for email and TXT Records for site verification.

The first step of the setup guide, 1. Copy your existing DNS Records, has an Open the DNS tab button on the Summary tab, which opens the DNS tab. On the DNS tab, the same step has a Scroll to DNS Records button, which scrolls down to the DNS records section. For the steps to add a record, please read our documentation on adding DNS Records.

A screenshot of the DNS tab on the Domain page shows the CloudCannon DNS heading with a change the DNS Provider link, and the setup guide with the Point pending-dns.com at CloudCannon DNS heading, the Update your nameservers step in progress, the 1. Copy your existing DNS Records step with a Scroll to DNS Records button, and the 2. Update your nameservers table with a required nameserver marked Update needed.
The setup guide on the DNS tab

Update your nameservers

The second step of the setup guide, 2. Update your nameservers, shows a table with one row for each nameserver. It lists each nameserver your domain needs under Required, the nameserver CloudCannon Found at your registrar, and a Status for each. A nameserver that matches shows Detected. The check passes only when your registrar lists exactly CloudCannon's nameservers. If your registrar lists a nameserver that CloudCannon DNS doesn't use, its row shows Remove.

Configuring your nameservers requires you to use the services provided by your domain registrar. For support, please contact your domain registrar.

CloudCannon DNS doesn't support DNSSEC. If DNSSEC is turned on for your domain at your registrar, turn it off before you update your nameservers. Otherwise, resolvers that check DNSSEC reject the answers from CloudCannon DNS, and your domain stops resolving for many visitors.

To update your nameservers:

  1. Log in to your third-party domain registrar with the account details used when you purchased your domain name. If you don't know who your domain registrar is, click the WHOIS link in the setup guide.
  2. Click the Copy icon next to a nameserver listed under Required. The icon will turn into a tick and show Copied!.
  3. Paste the nameserver at your domain registrar. Repeat steps 2 and 3 until your registrar lists every nameserver under Required, and remove any other nameservers.
  4. Save your changes at your domain registrar.
  5. Click the I've updated my nameservers button in the nameservers table.

CloudCannon will check your nameservers every hour, and email you when your domain uses CloudCannon DNS. There's no need to keep the page open. For how long CloudCannon checks hourly, and how to check again immediately, please read the section on how often CloudCannon checks your nameservers.

Most registrars hand your domain over to CloudCannon DNS within an hour, but it can take up to 48 hours.

A screenshot of the setup guide on the Summary tab shows the Waiting for CloudCannon nameservers on example.org heading, the Checking nameservers step in progress, and the Nameservers table with the two required nameservers and the two nameservers found, each marked Checking, and the Marked as updated and Check now buttons.
The setup guide while your nameservers propagate

If CloudCannon still can't see your new nameservers 48 hours after you clicked I've updated my nameservers, the setup guide lists what usually fixes it under How can I fix this?:

  • Check that the change was saved at your registrar, not only entered.
  • Replace all of the old nameservers. Adding CloudCannon's nameservers alongside them doesn't work.
  • If DNSSEC is on at your registrar, turn it off first.

Once you have fixed the problem, click the I've updated my nameservers button. CloudCannon will check every hour for another 48 hours.

If CloudCannon still can't see your nameservers after you have checked each of these, contact our friendly support team. Include your Base Domain, the name of your domain registrar, and the nameservers your registrar lists.

A screenshot of the setup guide on the Summary tab shows the heading example.org's nameservers do not match the CloudCannon nameservers, a note that CloudCannon has emailed the steps too and when the nameservers were marked as updated, the Nameservers do not match step in the tracker, the How can I fix this? notice, and the start of the Nameservers table.
The setup guide when your nameservers are not detected

When your nameservers switch while you have the Summary tab open, the setup guide shows [Base Domain] now uses CloudCannon DNS! Click the Add a Subdomain button to add a Subdomain, or the Dismiss button to close the guide. If you open the Summary tab after your domain goes live, CloudCannon shows the normal Summary tab.

The DNS tab keeps the setup guide once your domain is live, showing [Base Domain] uses CloudCannon DNS with three done steps, and the sentence below its heading says CloudCannon manages your DNS Records for [Base Domain]. Inside the guide, the nameservers collapse into a closed Nameservers row with a green tick, which reads CloudCannon detected the correct nameservers [time] ago. CloudCannon checks these every day. If the latest check failed, it reads CloudCannon could not check the nameservers [time] ago. instead, with when the nameservers were last correct. Click the row to open it and see the nameservers table.

A screenshot of the setup guide on the Summary tab shows example.org now uses CloudCannon DNS!, a three-step tracker with every step done, and the Next, host a Site on example.org section with the Add a Subdomain and Dismiss buttons.
The setup guide when your domain goes live
A screenshot of the DNS tab on the Domain page shows the CloudCannon DNS heading with a change the DNS Provider link, the setup guide with example.com uses CloudCannon DNS and three done steps, the closed Nameservers row with a green tick noting that CloudCannon detected the correct nameservers 12 minutes ago, and the Required records section noting that all three subdomains point at CloudCannon.
The DNS tab once the domain is live

If your nameservers change

If the nameservers of a live domain stop pointing at CloudCannon, the setup guide shows when CloudCannon noticed the change. As DNS caches expire, visitors stop reaching the DNS Records you store in CloudCannon, and reach the records at the new nameservers instead.

  • If you didn't mean to change your nameservers, change them back at your domain registrar, then click the I've updated my nameservers button.
  • If you moved your DNS on purpose, click the Open the Domain Settings tab button in the Do you now use a different DNS Provider? notice to open the Details section of the Domain Settings tab, and switch your domain to External DNS. This button requires the base-domain:settings:details:read permission.

Cloudflare deletes your domain's CloudCannon DNS zone if the nameservers stay changed for seven days. CloudCannon keeps a copy of your DNS Records when it notices the change. If you change the nameservers back after Cloudflare deletes the zone, CloudCannon creates the zone again and restores your records. Cloudflare may give the new zone different nameservers, in which case the setup guide shows the nameservers to set at your registrar.

A screenshot of the setup guide on the Summary tab shows the heading example.org's nameservers no longer point at CloudCannon DNS with the time CloudCannon noticed, the Do you now use a different DNS Provider? notice with an Open the Domain Settings tab button, and the Change the nameservers back table with each required nameserver, the nameserver found, and a Changed status.
The setup guide when your nameservers change

The I've updated my nameservers and Retry zone creation buttons require the base-domain:settings:dns:write permission. The Move to the new CloudCannon DNS button requires both the base-domain:settings:dns:write and base-domain:settings:details:write permissions. Without them, the buttons are disabled, and hovering over a disabled button shows You do not have permission to edit the DNS for [Base Domain]. or You do not have permission to edit the Domain Settings for [Base Domain]. Ask someone in your Organization who has these permissions.

A screenshot of the setup guide on the Summary tab shows the Point example.org at CloudCannon DNS heading, the 1. Copy your existing DNS Records step with an Open the DNS tab button, and the 2. Update your nameservers table with each required nameserver marked Update needed.
The setup guide without permission to edit the DNS

If you can't view the DNS of the Base Domain, the Summary tab replaces the setup guide with a CloudCannon DNS is not configured for [Base Domain]. notice. Domains on the legacy CloudCannon DNS show the setup guide instead.

How often CloudCannon checks your nameservers

CloudCannon checks your nameservers daily. It checks every hour until your domain is live, for up to 48 hours after the latest of these: you connected the domain, you set up CloudCannon DNS for it, or you clicked the I've updated my nameservers button. If your domain still isn't live after 48 hours, CloudCannon emails you and goes back to checking daily. Click the I've updated my nameservers button again to start another 48 hours of hourly checks.

The footer of the nameservers table says how often CloudCannon checks and when it last checked. Once your domain is live, the DNS tab shows this in the closed Nameservers row instead, and the footer keeps only its buttons. Click the Check now button in the footer to check immediately. For a minute after a check, the button is disabled, and hovering over it shows Checked less than a minute ago. You can check again in a minute. If CloudCannon couldn't complete the latest check, the footer shows Could not check with how long ago the check failed, and the status stays at the last known result.

View the nameserver check history

To see every recent check of your nameservers, click the View nameserver check history icon in the footer of the nameservers table. CloudCannon will open the Nameserver checks for [Base Domain] modal, which lists the nameservers your domain needs and the checks, most recent first. Back-to-back checks with the same result share a row.

Each row shows which DNS Provider the nameservers CloudCannon found belong to (CloudCannon DNS, Legacy CloudCannon DNS, or Another provider), Nothing found, or Couldn't check, along with the nameservers found, any error, and when the checks ran. A Couldn't check row doesn't change the status of your nameservers. Click the Load older results button to see older checks.

You can also list the checks with the CloudCannon API, at GET /api/v0/base-domains/{base_domain_uuid}/dns/checks.

Nameserver emails

CloudCannon emails everyone who can edit the settings of your Base Domain (the base-domain:settings:details:write permission) about the nameservers of your domain.

[Base Domain] now uses CloudCannon DNS

CloudCannon sends this email about 15 minutes after your nameservers switch to CloudCannon, if an earlier check found nameservers that didn't match. It lists what is live on up to four Subdomains under Subdomains live on [Base Domain], then, if they apply, Subdomains with errors, Subdomains without a valid SSL Certificate, Certificates still issuing, and Do you use email on [Base Domain]? when CloudCannon found no MX Records.

A screenshot of the email sent when example.com starts using CloudCannon DNS shows the headline example.com now uses CloudCannon DNS, a three-step tracker with every step done, the Subdomains live on example.com list with each Subdomain marked Live, the Subdomains with errors, Subdomains without a valid SSL Certificate, and Certificates still issuing lists, a note that CloudCannon found no MX Records, the Next actions, and the Open the Subdomains tab and Open the DNS tab buttons.
The domain is live email

[Base Domain]'s nameservers do not match the CloudCannon nameservers

CloudCannon sends this email when it still can't see your new nameservers more than 48 hours after you clicked I've updated my nameservers. If you didn't click it, CloudCannon counts the 48 hours from when you connected the domain or set up CloudCannon DNS for it, whichever is later, so switching a domain to CloudCannon DNS starts the 48 hours again. CloudCannon only sends the email within seven days of that starting point, and doesn't send it once your domain uses External DNS.

The email lists the nameservers your registrar still has and what usually fixes it, with an Open the Domain page for [Base Domain] button that opens your Domain page. Once your registrar lists the CloudCannon nameservers, click the I've updated my nameservers button on your Domain page, and CloudCannon will check every hour again.

A screenshot of the nameservers not detected email shows the headline example.com's nameservers do not match the CloudCannon nameservers, a tracker at Nameservers do not match, the nameservers required and the nameservers found marked Not CloudCannon DNS, the Next actions, the How can I fix this? list, and the Open the Domain page for example.com button.
The nameservers not detected email

Action required: [Base Domain]'s nameservers no longer point at CloudCannon DNS

CloudCannon sends this email when the nameservers of a live domain change away from CloudCannon. The email names the nameservers your domain uses now. If you didn't mean to change them, change them back at your domain registrar. If you now use another DNS Provider, switch your domain to External DNS on the Domain Settings tab of your Domain page. The email also says when Cloudflare will delete the zone if the nameservers stay changed, and that CloudCannon keeps a copy of your records to restore if you change the nameservers back. Click the Open the Domain page for [Base Domain] button to open your Domain page.

A screenshot of the nameservers changed email shows the headline example.com's nameservers no longer point at CloudCannon DNS, when CloudCannon detected the change, the nameservers required and the nameservers found marked Not CloudCannon DNS, the Next actions, when the CloudCannon DNS zone will be deleted, and the Open the Domain page for example.com button.
The nameservers changed email

Related Resources

Open in a new tab