Skip to content

DNS

RLNC provides DNS hosting using OpenStack Designate — see the upstream user guide for concepts and terminology.

Zones and recordsets can be managed in several ways, all of which are frontends for the same underlying API:

All zones are automatically signed with DNSSEC.

Service tiers

DNS hosting comes in three tiers, each with its own product name and set of published NS records:

Tier Product NS records
Basic NET.DNSBASIC
  • ns1.rlnc.no
  • ns2.rlnc.no
  • ns3.rlnc.no
Standard (default) NET.DNSSTD
  • ns1.rlnc.eu
  • ns1.rlnc.se
  • ns1.rlnc.no
  • ns2.rlnc.no
  • ns3.rlnc.no
Premium NET.DNSPREM
  • ns1.rlnc.global
  • ns1.rlnc.eu
  • ns1.rlnc.se
  • ns1.rlnc.no
  • ns2.rlnc.no
  • ns3.rlnc.no

See the service catalogue for pricing and SLA details for each tier.

NET.DNSSTD is used by default. To select NET.DNSBASIC or NET.DNSPREM instead, pass --attributes=product:NET.DNSBASIC or --attributes=product:NET.DNSPREM when creating the zone with the CLI, or set the equivalent product attribute when creating the zone via the API.

Service tier selection in the web UI

Setting the product attribute to select a non-default tier is not available in the web interface. Use the CLI if you need NET.DNSBASIC or NET.DNSPREM.

Changing tier

Changing a zone's tier after it has been created is an admin-only task. Please contact support if you need to do this.

Managing zones and recordsets

Creating a zone

openstack zone create --email hostmaster@example.com --attributes=product:NET.DNSPREM example.com.

The --email address is only used to populate the zone's SOA RNAME field.

In the web interface, go to Project → DNS → Zones in the left menu, then click Create Zone and fill out the popup.

Secondary zones not supported

RLNC does not support secondary-type zones. Only primary zones can be created.

Creating recordsets

Recordsets are created the same way, one per name/type combination:

openstack recordset create example.com. www.example.com. --type A --record 192.0.2.1
openstack recordset create example.com. www.example.com. --type AAAA --record 2001:db8::1 --record 2001:db8::2
openstack recordset create example.com. example.com. --type TXT --record '"v=spf1 -all"'

--record can be repeated to give a recordset multiple values, as shown above for the AAAA recordset.

In the web interface, click Create Record Set next to the zone in question.

Terraform / OpenTofu

The same zone and recordsets can be declared with the openstack provider's openstack_dns_zone_v2 and openstack_dns_recordset_v2 resources:

resource "openstack_dns_zone_v2" "example_com" {
  name  = "example.com."
  email = "hostmaster@example.com"

  attributes = {
    product = "NET.DNSPREM"
  }
}

resource "openstack_dns_recordset_v2" "www_example_com_a" {
  zone_id = openstack_dns_zone_v2.example_com.id
  name    = "www.example.com."
  type    = "A"
  records = ["192.0.2.1"]
}

resource "openstack_dns_recordset_v2" "www_example_com_aaaa" {
  zone_id = openstack_dns_zone_v2.example_com.id
  name    = "www.example.com."
  type    = "AAAA"
  records = ["2001:db8::1", "2001:db8::2"]
}

resource "openstack_dns_recordset_v2" "example_com_txt" {
  zone_id = openstack_dns_zone_v2.example_com.id
  name    = "example.com."
  type    = "TXT"
  records = ["\"v=spf1 -all\""]
}

Updating or deleting a zone or recordset this way follows Terraform/OpenTofu's normal workflow: change or remove the resource block and re-apply.

Updating recordsets

To update a recordset, look up its ID and use openstack recordset set:

ID=$(openstack recordset list example.com. --name www.example.com. --type A -c id -f value)
openstack recordset set example.com. $ID --record 192.0.2.2

In the web interface, click the zone's name, go to the Record Sets tab, then click Update next to the recordset in question.

recordset set replaces, it does not add

openstack recordset set replaces all existing values for the recordset with whatever --record options are given. To add a value, repeat all of the recordset's pre-existing values alongside the new one.

Deleting recordsets

Look up a recordset's ID with openstack recordset list, then delete it. Cleaning up the recordsets created above:

ID=$(openstack recordset list example.com. --name www.example.com. --type A -c id -f value)
openstack recordset delete example.com. $ID

ID=$(openstack recordset list example.com. --name www.example.com. --type AAAA -c id -f value)
openstack recordset delete example.com. $ID

ID=$(openstack recordset list example.com. --name example.com. --type TXT -c id -f value)
openstack recordset delete example.com. $ID

In the web interface, click the zone's name, go to the Record Sets tab, then choose Delete from the drop-down menu next to the recordset in question.

Deleting a zone

openstack zone delete example.com.

Deleting a zone also deletes all of its recordsets, so the recordset deletions above aren't strictly necessary before deleting the zone itself.

In the web interface, choose Delete from the drop-down menu next to the zone in question.

Registry onboarding

Creating a zone in RLNC does not register it in the TLD registry, and does not update the parent zone's NS/DS delegation records to point to RLNC.

  • If Redpill Linpro is already the registrar for the zone, or you want us to become the registrar, contact support with that request.
  • If the zone uses a third-party registrar, you must update its NS/DS records yourself, using the NS records for your chosen tier above. For the DS record, query the zone's CDS record directly from one of its nameservers, e.g. dig CDS example.com @ns1.rlnc.no, and upload that as the DS record at the registry.

If the DS record is never uploaded to the parent registry, the zone still resolves normally — DNSSEC signatures just can't be validated.