Koapanel
IT Try it free
All manual sections

DocumentationDNS and providers

DNS and providers

The panel can manage the DNS of your domains when it is at Cloudflare or 1PrimeCDN: you see the records, edit them, and point a site to this server with one click.

Connecting Cloudflare

You need an API token with the minimum permissions. On Cloudflare:

  1. Open dash.cloudflare.com › My Profile › API Tokens and press Create Token.
  2. Pick the Edit zone DNS template (or Custom token).
  3. Set two permissions: Zone · Zone · Read and Zone · DNS · Edit.
  4. Under Zone Resources choose Include › All zones or only the zones you want to manage.
  5. Create the token and copy it (Cloudflare shows it only once).

In the panel open DNS, press Connect Cloudflare, paste the token and press Check and connect: the panel checks right away that it works (it lists your zones) and stores it encrypted on the server. Do not use the “Global API Key”: a token with two permissions is safer and can be revoked in a moment.

Connecting 1PrimeCDN

Press Connect 1PrimeCDN and paste the API key of your account. If 1PrimeCDN has not published its DNS API yet, the connection is saved with the status Waiting for the 1PrimeCDN API: when it is available press Check and the zones appear.

Who sees what

Every account connects its own providers and sees only its own connections. Those created by an administrator serve every site of the administrators. You can change records only in zones that contain one of your sites.

Records

From DNS press Manage records next to a zone: the table of records has a type filter and search. You can add, edit and delete A, AAAA, CNAME, MX, TXT, SRV, CAA and NS records, choose the TTL (Auto = decided by Cloudflare) and, for A/AAAA/CNAME, whether traffic goes through the CDN (Cloudflare's orange cloud, 1PrimeCDN's “Through the CDN”). The panel checks values before sending them (an A needs an IPv4, an MX a host name…).

Export downloads the zone in BIND format; Import accepts a zone file, first shows what would be added and skips records already present.

Point to server

Open the site and the DNS tab: you see where the domain and www point and whether they lead to this server. If not, press Point to server: the panel lists the changes (A/AAAA records set to the server address, old or conflicting records removed) and applies them only when you confirm. Other records (email, verifications) are not touched.

Going through the CDN stays off by default: Let's Encrypt checks the domain over HTTP and the proxy may make the check fail. Turn it on after enabling HTTPS.

Check shows what the public DNS of Cloudflare (1.1.1.1) and Google (8.8.8.8) answer now: after a change it can take from a few seconds to a few hours, depending on the TTL.

HTTPS and DNS

When you press Get a free certificate, the panel first checks that the domain points to the server. If it does not and the DNS is at a connected provider, it offers Fix DNS and enable HTTPS. If the domain goes through the Cloudflare proxy you can remove it during activation or keep it: Cloudflare usually lets the Let's Encrypt check through (/.well-known/acme-challenge/), but special security rules (“Always Use HTTPS” on HTTP, firewall, “Under Attack”) can block it.

Server address (administrators)

At the bottom of the DNS page the administrator sees and can set the public IPv4/IPv6 address of the server. If it is not set, the panel uses server.public_ip from the configuration or the public addresses found on the network interfaces.