DNS

Introduction

Futrou provides DNS hosting for your domains: create a zone, add records, and point your domain’s nameservers at Futrou to make it live.

DNS zone

A DNS zone holds all the records for one domain, scoped to a project like any other service. Click Create DNS zone from the project’s DNS page, give it the domain name, and Futrou automatically adds a starter set of records: an SOA record, NS records pointing at Futrou’s nameservers, and a _futrou TXT record used to verify you control the zone.

To actually use Futrou’s DNS for a domain, set the nameservers shown in the zone to your domain registrar. This is separate from adding the zone itself — until the nameservers are updated at the registrar, the records you create won’t be used by the rest of the internet. If you don’t already own the domain, see Domains for choosing a registrar.

Each zone in the list shows its region and record count, with Edit to open the zone editor, a refresh action to re-check its status, and delete.

Metrics

The DNS overview shows aggregated metrics across every zone in the project, over a selectable time window (Last 24 hours by default):

• Queries — total DNS queries answered, with the min/max seen in the window.
• Avg Latency — the average server response time for a query.
• Error Rate — the percentage of DNS lookups that failed.

Below the metric cards, a bar chart breaks queries down by record type (A, AAAA, NS, MX, TXT, CNAME, DNSKEY, SOA, HTTPS, CAA, SRV, and others), so you can see at a glance what kind of traffic your zones are actually serving.

DNS records

Records are individual entries in a zone that define how a domain and its subdomains behave. Each record has a type, a name, a value, and a TTL.

Add a record with the form at the top of the zone editor — pick a Type, fill in Name and Value, and choose a TTL (or leave it on Auto). The records table below lists every record in the zone, searchable by name or value, with edit and delete actions on each row.

Tip: After changing a record, it can take anywhere from a few minutes to a few hours for the change to propagate across the internet, depending on the TTL and how long resolvers cache the old value.

Supported record types

• A — maps a name to an IPv4 address. Example: example.com. IN A 159.69.119.71

• AAAA — maps a name to an IPv6 address. Example: example.com. IN AAAA 2a01:4f8:c010:d03::1

• CNAME — aliases one name to another. Can’t be used on a zone’s apex, only on subdomains. Example: www.example.com. IN CNAME example.com.

• ALIAS — like CNAME, but usable on the zone apex.

• MX — mail servers for the domain, each with a priority (lower number = higher priority). Example: example.com. IN MX 10 mail.example.com.

• TXT — arbitrary text, commonly used for domain verification, SPF, and DKIM. Example: example.com. IN TXT "v=spf1 include:_spf.google.com ~all"

• NS — delegates a name to other nameservers.

• SRV — locates services (host and port) for a name, with priority and weight.

• CAA — restricts which certificate authorities may issue TLS certificates for the domain.

• PTR — maps an address to a hostname (reverse DNS).

• SOA — zone metadata: primary nameserver, admin contact, serial number, and timing values. Created automatically and rarely edited by hand.

• SVCB / HTTPS — service binding records used to advertise HTTP-related connection parameters (such as HTTP/3 support) directly in DNS.

TTL

TTL (Time To Live) controls how long resolvers may cache a record before checking for an updated value. Lower TTL means changes take effect faster but resolvers query more often; the default is 300 seconds.

Nameservers

Every zone lists the nameservers you need to configure at your domain registrar to make Futrou authoritative for the domain — order doesn’t matter. This change can take up to 48 hours to fully propagate; during that time some visitors may still see the old DNS answers while others see the new ones. For .cz domains, you can instead set a single NSSET at your registrar: FUTROU-CLOUD.

Import and export

A zone can be exported as a standard BIND zone file, and a zone file can be imported to bulk-create records — useful when migrating a domain from another DNS provider.

Purging

If a change isn’t showing up as expected, purging a zone clears Futrou’s own DNS cache for it, forcing the next queries to resolve fresh.

Limits

A single zone supports up to 3,500 records, or 2 MiB of zone data, whichever is reached first. See Limits for this and other platform-wide numeric limits.

Pricing

DNS zones are billed per month, shown on the zone’s page — see Billing for how workspace credit is charged.