How to manage domains and DNS in Kiravo

Open your website in the hosting control panel and choose Domains. This area manages the domains attached to that website and their hosting settings. Domain registrations and renewals are managed separately in the Kiravo client area.

The Domains list

The list shows Domain, Type, DNS status, Document root, and a three-dot menu for each entry. The primary domain is marked PRIMARY. A platform preview address can appear as PREVIEW and use the same document root.

Open a domain’s three-dot menu → Manage to view its settings. Check the domain before editing, especially when a website has several aliases or subdomains.

The panel’s DNS settings affect public lookups only when the domain, or the relevant delegated zone, uses those authoritative nameservers. If DNS is hosted elsewhere, edit the records at that provider. See Point your domain to Kiravo before changing nameservers or website addresses.

Add a subdomain or domain alias

Click Add domain. Add new domain offers three choices: Addon, Subdomain, and Alias. Check the allowance displayed for the selected type before continuing. Adding a domain here does not register it or change nameservers at an external registrar.

Addon

Use Addon for another domain that serves different content from its own document root within this website.

1. Select Addon.
2. Enter the domain in Domain, without the www. prefix already shown beside the field.
3. Set Document root to the directory containing that domain’s files. The form already shows a leading /.
4. Review the domain and directory, then click Add.

An addon domain shares the parent website’s hosting environment. Use a separate website when the project needs its own website-level settings and resources.

Subdomain

Use Subdomain for a prefix under the parent domain shown in the form, such as blog.example.com. A subdomain can use a separate document root.

1. Select Subdomain.
2. Enter only the prefix in Domain. For blog.example.com, enter blog when the suffix shown is .example.com.
3. Set Document root to the directory the subdomain should serve.
4. Review the completed name and directory, then click Add.

Check the subdomain’s public DNS after creation. If the parent domain uses an external DNS provider or the subdomain has its own delegation, configure the required records there rather than assuming the panel updates that provider.

Alias

Use Alias for another domain that shares the primary domain’s document root and serves the same content.

1. Select Alias.
2. Enter the alias in Domain, without the www. prefix already shown beside the field.
3. Select Redirect to the primary domain if visitors should be redirected to the primary address. The checkbox is off initially.
4. Review the domain and redirect choice, then click Add.

Connect the alias domain through its own DNS provider or registrar. Adding it to the website does not automatically connect a separately registered domain.

Change the document root

In the domain’s Manage page, choose Document root and click the pencil beside the current directory. The dialog shows the domain, the existing directory, Cancel, and Save. Enter the directory relative to the leading / shown in the form.

Changing the document root changes the directory used to serve that domain. Check that the intended files are present before saving. Use Manage files to inspect the directory.

Manage DNS records

Open the domain’s three-dot menu → Manage, then choose DNS records in the section navigation. The table has Type, Host, Value, TTL, and a row menu. Use search, Show, and Page to find a record before adding a duplicate.

What each column means

Column	Meaning
Type	The kind of record. Common examples include A, AAAA, CNAME, MX, and TXT.
Host	The name within the zone. @ represents the domain itself; www represents its www subdomain.
Value	The address, target hostname, or text associated with the record. The input fields depend on its type.
TTL	How long a DNS answer can be cached. The table shows the value in seconds, such as 300s.

Lowering a TTL does not remove answers already cached under an earlier TTL. Plan DNS changes before moving a live website or email service.

Add a DNS record

1. Click Add record.
2. Select Type. The form explains the selected record type.
3. Enter Hostname. Use @ for the domain itself or a relative name such as www.
4. Complete the type-specific fields. An A record uses IPv4 address. An MX record uses Priority and Target domain. Use the values supplied by the service you are connecting.
5. Review TTL. Use zone default is on initially and shows the zone’s current default, 300s in this example. Switch it off in the form if you need to choose a different TTL.
6. Review the name, type, value, and TTL, then click Create. Check for confirmation or validation errors and find the resulting record in the table.

The values shown for another website are not connection settings for your domain. Use the IP addresses or records provided for your own website or external service.

Edit or delete a record

Open the record’s three-dot menu → Edit. Edit record contains the current values and a Save button. Review the complete record before saving, or choose Cancel to leave it unchanged.

Delete is available from the row menu and the edit form. Copy the record’s type, host, value, priority if applicable, and TTL before deleting it.

Caution

Changing or deleting DNS records can interrupt the website, email delivery, or domain verification. Check existing A and AAAA records, mail MX records, and authentication records before replacing them. A successful save in the panel does not confirm that public DNS has updated.

Gmail auto-configuration

Below the records, Auto configuration includes a Gmail → Configure now helper. Its description refers to configuring the domain’s MX records for Gmail.

Use the current setup instructions from your email provider before applying automatic configuration. Check which existing records it will replace and whether DNS is authoritative here. Do not assume this helper also completes SPF, DKIM, or every verification step required by your provider.

Enable DNSSEC

Choose DNSSEC in the domain’s section navigation. The card has a DNSSEC switch and explains that the feature requires support from your registrar.

DNSSEC signs DNS data so validating resolvers can check its authenticity. For a registered domain, the chain of trust also requires the corresponding DS information in the parent zone, normally submitted through the registrar.

Before enabling the switch, confirm that Kiravo hosts the authoritative zone and that your registrar supports publishing the required DS record. Complete the registrar’s setup with the values supplied by the DNS provider. If the required values are unavailable, contact support before proceeding.

Caution

The panel switch alone does not confirm that DNSSEC is working. A DS record that does not match the active DNS provider can make the domain fail DNS validation. Coordinate DNSSEC when changing nameservers and verify the resulting public configuration.

Mail routing and DKIM

Mail routing settings controls how the hosting system treats incoming mail. Email authentication contains the DKIM setting for outgoing mail. Review them separately when connecting an email service.

Choose between local and remote mail

Open Mail routing settings and choose the option matching the service receiving mail for this domain:

• Local mail means you use this hosting package to receive inbound email. Manage its mailboxes under Emails.
• Remote mail means a third-party email server receives inbound email, such as Google Workspace or another email provider.

Check the selected option and any confirmation shown when making a change. Review the public MX records as well. Changing this routing setting does not by itself migrate mailbox contents or prove that the external provider is ready.

Caution

Plan the mailbox migration and DNS changes before switching providers. Keep access to existing messages and test delivery after the change. Avoid changing routing on a working domain just to test the interface.

Enable DKIM and mail routing

Under Email authentication, use the switch beside DKIM to manage signing for mail sent through the hosting service. Check any DNS records required by the panel and verify them at the authoritative DNS provider. If DNS is hosted elsewhere, changing a setting here does not update that external provider automatically.

If another provider sends mail for your domain, configure DKIM with that provider and publish its required records. Remote mail describes incoming routing; it does not determine which service signs every outgoing message.

After setup, send a test message and check its authentication results. DKIM is part of email authentication alongside SPF and DMARC; enabling it does not guarantee inbox placement.

Delete a domain

Delete is available in the domain’s row menu and at the bottom of its Manage page. Check the exact domain and any confirmation before proceeding. Removing a domain from hosting is separate from cancelling its registration at the registrar.

Before deleting, preserve the DNS values and take a manual backup of any website data you need. Do not assume that removing a domain preserves or removes every associated file, mailbox, or configuration item. Review the confirmation and contact support if the scope is unclear.