Record Sets

A Record Set groups all entries with the same name and the same type. www of type A with three IP addresses is one record set with three values — not three entries. The whole set is always stored and written to the provider as a unit.

The editor

Open zone → Create record set (or edit a row). The editor knows the common types and offers matching fields instead of a free-text box:

• A / AAAA — addresses as chips; when creating an A record, its AAAA twin can be created right along with it
• MX — priority and mail server per row; the target suggests matching sources as you type
• SRV — priority, weight, port, and target as structured fields
• TXT / CAA — multi-line field, quotation marks are set correctly on save
• CNAME, NS, PTR and other types as a value list

The name field is called Label and shows on the right the domain it is appended to. @ stands for the zone itself.

Examples of typical record sets:

Label	Type	Values	Result
@	A	203.0.113.10	example.com points to the IP
www	CNAME	example.com.	www.example.com follows the main domain
@	MX	10 mail.example.com · 20 backup.example.com	two mail servers with priorities
@	TXT	v=spf1 mx -all	SPF: only the MX servers may send
_dmarc	TXT	v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com	DMARC policy
_sip._tcp	SRV	10 60 5060 sip.example.com	SIP service with priority/weight/port
home	A	(bound to a DynDNS target)	follows the reported router IP

Each type comes with a short explanation in the editor, linking to the detailed description in the in-app docs at /docs.

The $domain placeholder

In values, $domain stands for the name of the target zone. In Sync Groups and Templates this is the heart of the matter — the same set then fits many zones. The placeholder is also substituted when editing directly in a zone.

Profiles

For the typical email entries there are guided profiles instead of hand-crafted TXT values:

Profile	Entry
SPF	@ TXT
DMARC	_dmarc TXT
DKIM	<selector>._domainkey TXT
MTA-STS	_mta-sts TXT
TLS-RPT	_smtp._tls TXT
BIMI	default._bimi TXT

In the editor you pick the profile, fill in the fields (such as policy and reporting address for DMARC), and get the finished value. Existing entries are recognized and opened for editing in profile mode.

Email base setup

The Email base setup bundle applies the essential entries in one go. If any of them collides with an existing entry, the operation is blocked and the affected names are listed — nothing gets overwritten in passing.

Applying at the provider

Saved changes go to the provider immediately. If that fails, the desired state remains stored nonetheless and the provider’s error message appears in the interface; the next reconciliation catches up on the difference.

Import and export

Per zone (BIND): In the zone detail, Export downloads the entries as a BIND zone file. The export asks whether sync group entries and DynDNS entries should come along — unchecked, the file contains only directly entered records (including source-bound entries with their current values). Import reads a BIND file; comments, $TTL/$ORIGIN and wildcards are understood, SOA and apex NS are skipped visibly (the provider manages them), and names outside the zone become a note instead of a wrong entry. Same-key collisions follow the overwrite choice known from templates.

Many domains (CSV): At the top of the zones page, Export (CSV) writes selected domains into one file — columns DOMAIN,HOST,TYPE,ANSWER,TTL,PRIO, the common registrar layout, one row per record value; MX/SRV priority lives in the PRIO column. Import (CSV) distributes such a file over the project’s zones and reports per domain what was applied; domains the project does not manage show up as errors instead of vanishing silently.