Skip to content

DNS (Cloudflare and Bunny)

Netkeel does not host DNS. Your domain’s DNS stays with your provider. If that provider is Cloudflare or Bunny, you can connect your own account and Netkeel creates the DNS records of your applications for you, instead of you copying them by hand. See DNS records for the records themselves.

Everything happens inside your account, with the permissions of the token or key you give. Netkeel does not run a CDN of its own.

Only the account owner and super admins can use this tab.

  1. In the sidebar, open Integrations, then DNS.
  2. Under Choose your DNS provider, click Cloudflare or Bunny DNS.
  3. Follow the steps shown on screen to get a token or key, then paste it into the field.
  4. Click Connect.

Netkeel checks the credentials and lists your zones before it saves anything. If the check fails, nothing is stored.

You can connect one account per provider. To add the second provider, use Connect another provider. When both are connected, each domain uses the account that holds its zone. If a domain matches zones in both, the most specific zone wins, so shop.example.com uses a shop.example.com zone before example.com.

Create a custom API token at Cloudflare API tokens and, under Zone Resources, limit it to the zones you want Netkeel to use. Give it these permissions:

  • Zone → Zone → Read
  • Zone → DNS → Edit
  • Zone → Cache Purge → Purge

If Cloudflare refuses a change because a permission is missing, the connection shows Needs permissions. Create a new token with all three permissions and connect it again.

Copy the API key from your Bunny account settings. A Bunny API key belongs to the whole account and cannot be limited to one zone or to DNS. Netkeel only uses it for the zones of your applications’ domains, but treat the key like a password. If you want to give Netkeel less access, use Cloudflare, whose tokens can be limited to specific zones.

The token or key is stored encrypted. After you connect, the panel only shows the last four characters. It is never shown again.

If a provider stops accepting the credentials, the connection shows Credentials no longer work. Disconnect it and connect new ones. Applications on your other connection keep working.

The Applications card on the DNS tab lists every application that has a domain of its own, with its zone, the provider and a DNS status:

Status Meaning
Records OK The domain’s records point at the application’s server.
Records missing There are no records for the domain yet.
Points elsewhere The records point at another address.
Not in a connected account None of your connected accounts holds the domain’s zone.
Server not ready The server has no address yet.
Could not check The provider did not answer. Click Refresh.

Applications that are still on a Netkeel preview address are not listed.

  1. Click Set up DNS on the application’s row.
  2. Read the plan. Records to create are new records. Already correct records are left alone.
  3. Click Apply.

Netkeel creates an A record for the domain and one for www that point at the application’s server (plus AAAA records when the server has an IPv6 address). The records carry the note “Managed by Netkeel”. If you run Set up DNS again, nothing that is already right changes.

Records are created as DNS only. On Cloudflare you can tick Proxy through Cloudflare in the plan. Taking an application live needs the domain to resolve to your server, so it is best to turn the proxy on after the application is live. Once the certificate is issued, set SSL/TLS to Full (strict) in Cloudflare, or visitors may see redirect loops. Bunny DNS has no proxy option.

If a record already exists with a different value, the plan lists it under Existing records that differ. Nothing in that list changes unless you tick it. A ticked record is replaced, or removed if it is in the way of an A record. An unticked one is reported as left alone, and the A record waits until you tick the record in its way.

Before Netkeel changes a record it did not create, it keeps the record’s previous value, so you can put it back later.

If your provider has a cache for the domain, two things can clear it:

  • Click Purge cache on the application’s row, then Clear cache. Cloudflare clears the domain and www. Bunny clears https://example.com/* and https://www.example.com/* in your CDN pull zones.
  • Switch on Clear cache after each deploy or update for the application. Netkeel then clears the cache after a successful Git deployment or after a Drupal or Joomla update.

The automatic clearing never slows down or fails a deployment. If it fails, the reason is added to the application’s activity. It runs at most once a minute for each zone.

If Cloudflare refuses to clear by hostname, Netkeel asks a second question before it clears the whole zone (“This purges the whole zone”). It never clears a whole zone without that confirmation.

On Bunny, if you only use Bunny for DNS and no pull zone serves the domain, the panel says there is nothing to clear. That is not an error.

Remove Netkeel’s records and undo replacements

Section titled “Remove Netkeel’s records and undo replacements”

Click Remove Netkeel’s records on an application’s row. The button appears once Netkeel has created or changed records for it. The plan shows:

  • Records to delete: records Netkeel created.
  • Records to put back: records Netkeel replaced, set back to their original value, or created again if Netkeel had removed them. This is on by default through Restore replaced records to their original values. Untick it to leave them as they are.
  • Left alone: records you changed since, which Netkeel will not touch. Tick Remove anyway (or Restore anyway) next to a record if you want it handled after all.

Click Remove records to confirm. Run it twice and the second run does nothing.

Deleting an application does not remove its DNS records.

When you move an application to another server, its DNS records are not changed. The status shows Points elsewhere. Click Set up DNS again to point the records at the new server. The cache setting follows the application.

  • It never changes MX or TXT records, or any record type other than A, AAAA and CNAME, and never touches names other than the application’s domain and its www.
  • It never edits or deletes a record it did not create unless you tick that exact record.
  • It never changes zone settings, such as the SSL/TLS mode, rules or caching.
  • It never clears a whole zone without a second confirmation.
  • It never deletes records when you disconnect, unless you tick Also remove the records Netkeel created.
  1. On the DNS tab, click Disconnect next to the provider.
  2. Optionally tick Also remove the records Netkeel created. Records you let Netkeel replace go back to their original values. A record you edited since is left alone.
  3. Click Disconnect.

Netkeel forgets the credentials and stops clearing the cache. Without the tick, the DNS records it already created stay in your account.