GigakubeWikigigakube.ch →Menu ↓

DNS

Zones and records for your domains, on our nameservers or on your Cloudflare account, and what to set at your registrar.

Two places to keep a zone

A DNS zone (for example example.ch) belongs to a project and lives in one of two places:

The domain does not have to be registered with us: you can create a zone for any domain you own.

To create zones on our nameservers, the project's cloud must be switched on (Getting started).

Creating a zone

From the DNS menu, Add zone:

  1. Domain: the domain name, without www (for example example.ch);
  2. Where the zone lives: Our nameservers, or one of your connected Cloudflare accounts;
  3. the project, if you have more than one;
  4. Create.

The zone starts with the records that cannot be touched (the apex SOA and NS, marked managed by us) and nothing else.

You cannot create zones:

A project can have up to 50 zones on our nameservers.

Making the zone live: nameservers at the registrar

A zone only works once the domain points to its nameservers. This is done at whoever registered the domain (the registrar: us, if you registered it here, or whoever holds it today), not in DNS.

For a zone on our nameservers, set these at the registrar:

ns1.gk01.ch
ns2.gk01.ch

The Copy the nameservers button copies them.

Next to each zone, the panel checks the delegation by asking the domain's registry directly:

In the panel Meaning What to do
live here The domain points to the right nameservers Nothing
points elsewhere The registry publishes other nameservers Change them at the registrar. If you want a quick switchover, lower the TTL at the old provider the day before
not pointed yet The registry publishes no nameservers The domain is not registered, or has just been registered and the registry has not published the delegation yet
DNSSEC blocks it The domain points to us, but the registry still publishes a DNSSEC signature from the previous provider Switch off DNSSEC at the registrar: we do not sign zones, and with that signature most of the internet answers with an error (SERVFAIL). It usually sorts itself out within a few hours
not checked The check did not succeed Try again later

Records

With a zone open, Add record:

Then Save. A record is the set of values with the same name and type: saving it replaces all the values for that name and type. Edit record and Delete record work on that set.

Type Example value Notes
A 203.0.113.10 IPv4 address
AAAA 2001:db8::10 IPv6 address
CNAME www.example.net Alone on its name, never on the root
MX 10 mail.example.ch Priority and mail server
TXT v=spf1 mx -all Printable text, up to 4000 characters
SRV 10 5 5060 sip.example.ch Priority, weight, port, target
CAA 0 issue "letsencrypt.org" Who may issue certificates
NS ns1.other.example Only below the root, to delegate a subdomain

The apex SOA and NS cannot be changed. A zone can have up to 1000 records.

Pointing a domain at one of your servers in one click

Point at an address writes an A record on the root and one on www, both to the same address: that is what most websites need. Choose One of your public addresses (the public addresses of the project's servers, with the server name) or Type an address instead, then Point it. Afterwards, the two records can be changed or removed like any other.

Moving and deleting

Cloudflare

To manage from here a zone that lives on your Cloudflare account:

  1. in Cloudflare: My Profile → API Tokens → Create Token → Custom token, with these permissions: - Zone · Zone · Read - Zone · DNS · Edit - Zone · Zone · Edit, only if you want to create new zones from here

Restrict it to the zones or the account you want us to see; 2. in DNS, Cloudflare accounts section, Connect Cloudflare: a name for the connection, the project and the API token, then Check and connect.

We check the token with Cloudflare straight away, keep it encrypted and never show it again, not even to you. Connecting an account needs Can manage.

Then, in Add zone, choose that connection in Where the zone lives: if the zone already exists on your account we connect it, otherwise we create it (this needs the Zone · Zone · Edit permission). For zones on Cloudflare, SRV and CAA records are read-only here: change them in Cloudflare.

Disconnect forgets the token; a connection that still has zones here cannot be removed.

Costs

A zone on our nameservers is charged by the hour, for as long as it exists (see Billing and invoices). Zones on Cloudflare are not.

For developers

Open to API keys and to the MCP:

What Method MCP tool Role
The project's zones Dns/getZoneList cloud_get_dns_zones viewer
A zone's records Dns/getRecords (zone or uuid) cloud_get_dns_records viewer
Write a record Dns/setRecord (zone, name, type, records, ttl?) cloud_set_dns_record operator
Delete a record Dns/deleteRecord (zone, record_id) cloud_delete_dns_record operator

The zone is given by name (example.ch) or by its uuid. record_id is <full name>/<TYPE>, as returned by Dns/getRecords (for example www.example.ch/A). records is a list of 1–20 values; without ttl the record keeps the one it had, or the zone's (usually 3600). Writes accept dry_run.

curl -s https://gigakube.ch/api/rpc \
  -H "Authorization: Bearer $GIGAKUBE_API_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"Dns/setRecord","params":{"call_data":{"zone":"example.ch","name":"www","type":"A","records":["203.0.113.10"],"ttl":300}}}'

With an API key (not with the MCP) zones too: Dns/getProviders and Dns/getDelegation (viewer), Dns/createZone (name, provider?), Dns/deleteZone and Point at an address Dns/pointTo (operator), Dns/moveZone and the Cloudflare connections Dns/addProvider, Dns/deleteProvider (admin).