Domains and DNS

Every public name in Velrix, an app’s hostname, a site’s name or a mail domain, sits under a domain its owner has proved. Prove a domain once and use any name under it. Velrix can also register domains for you and serve their DNS.

Prove a domain

1. Open Domains in your account (under Domains and network), or your organisation’s Edge tab for its domains.
2. Add the domain, such as example.se.
3. Velrix shows a TXT record and its value. Set it where the domain’s DNS is kept, then choose Verify.

The domain then says Verified, and names under it, such as www.example.se or shop.example.se, can go on your apps and sites. Velrix looks again from time to time: if the TXT record goes away, you are told, and names under the domain stop being served a while later unless it comes back.

A domain you bought through Velrix is proved by that alone.

Redirects on the same page send a name under a verified domain to any https:// address, with no app behind it.

Buy or transfer a domain

Where your operator sells domains, the Domains app has Find a domain: type a name or a word to see what is free and what it costs a year.

• Buy opens the order inline: the period, the holder from your Contacts, nameservers (leave them empty to use the realm’s DNS), Renew automatically, and the registry’s terms to accept. The price is held on your account first and charged once the registry says the domain is yours; a refused order is never charged.
• Transfer in takes the domain’s auth code from its current registrar instead.

Each domain has a page: its status and dates, auto-renew, the registrar lock, nameservers, DNS records, DNSSEC and history. You are reminded 60, 30, 7 and 1 days before a domain runs out. With auto-renew on, it is renewed 30 days ahead. Transfer shows the auth code once, to move the domain elsewhere; deleting a domain needs its name typed back, and can’t be undone.

DNS on Velrix

A domain on the realm’s DNS resolves at once. Its page lists two kinds of records:

• Generated records, locked, with where they come from: the address of each app and site name under the domain, its HTTPS record (so browsers use HTTP/3 from the first visit), and the records your mail domains need. They follow your apps by themselves.
• Your records: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, HTTPS and SVCB. Add record, then save the set.

Zones are signed with DNSSEC (ECDSA P-256, NSEC3); the domain’s DS record goes to the registry by itself for a domain bought here.

Only the DNS: a domain held elsewhere

Keep your registrar and let Velrix serve the domain’s DNS:

1. Prove the domain as above.
2. In Domains, choose Add DNS zone for it. It shows as DNS only.
3. At your registrar, point the nameservers at the ones the zone shows.

The proof’s TXT record is in the zone Velrix serves, so once the nameservers point here the domain keeps proving itself. Point them away and it is no longer proved.

DNSSEC without a gap: remove the old DS record at your registrar, point the nameservers here, then add the DS the zone shows.

Moving from DirectAdmin, velrix import directadmin brings the zones across (The velrix command).