DNS Service (Designate)
Overview
Using the firstcolo Cloud DNS service you can rely on our authoritative DNS infrastructure and experience for your domains and records.
The service is based on and compatible with the OpenStack Designate project and therefore supported by various clients and tools.
You can manage DNS zones and records both via our public OpenStack API endpoints, as well as using the Dashboard.
The DNS service is shared between all regions. You will need to choose a region in the Dashboard or using the OpenStack CLI environment variable OS_REGION, but it does not matter which one you choose. DNS objects are always global.
Feature Support Matrix
| OpenStack Designate Feature | eu-central-1 region |
|---|---|
| Manage zones and recordsets | Yes |
| Zone transfer to different projects | Yes |
| Secondary Zones | Yes |
| Zone Import / Export | Yes |
| PTR records for Floating IPs | Yes* |
*Using the Neutron DNS integration (more information in the section PTR records for Floating IPs)
Manage zones and recordsets
A zone object represents a DNS Zone, e.g. your domain name and your subdomain names. If you want to use the firstcolo Cloud DNS service for your domain, you need to delegate it to our DNS servers.
A recordset object represents DNS records. One recordset usually consists of a name (e.g. example.com. or www.example.com.). a type (e.g. A for IPv4 records) and one or more records (e.g. 10.0.0.1 and 10.0.0.2).
To find out more on how you can do this, see our tutorial and howto guide.
!! Please note that DNS zones in the firstcolo DNS service must be fully qualified, which means they must end with a trailing dot. If your domain name is example.com, the corresponding fully qualified zone name would be example.com.
Zone transfer to different projects
It is possible to transfer zones if they need to be maintained using different OpenStack projects. For example you can have a zone named company.com. in project-a and another zone named team-1.company.com. in project-b.
Zone disputes
It is not automatically possible for us to verify ownership of your domain names, so in very rare circumstances your domain name might have been claimed by another customer already. Please contact our customer support in this case.
Secondary Zones
It is possible to use our authoritative name server infrastructure together with a hidden master that you maintain yourself. You can accomplish that by creating a secondary zone. Using the OpenStack CLI you can create it like this: openstack zone create --type secondary --masters master-1.example.com. master-2.example.com.
Our authoritative name servers will respect the Refresh, Retry, Expire and TTL timings in the SOA record as specified by the configured DNS master and our servers will poll for updates using the AXFR protocol accordingly. You can expect the AXFR to originate from one of our public authoritative DNS servers (ns1.cloud-fc.de, ns2.cloud-fc.de).
Sending the NOTIFY message to our DNS servers is not supported.
Zone Import / Export
To migrate large amounts of zones and records to the firstcolo Cloud DNS service, it is possible to use our Import / Export functionality. It is using the master file format as specified in RFC 1035.
PTR records for Floating IPs
It is possible to configure PTR records for Floating IPs. This is accomplished using the Neutron DNS integration. For more information, please refer to our Network reference guide and our How-to guide for setting up PTR records for existing floating IPs.
It is not possible to set arbitrary PTR records via the Designate API directly (e.g. using openstack ptr record set).