How to register private nameservers

Use private nameservers when you operate authoritative DNS servers under your own domain. For example, you can register ns1.example.com and ns2.example.com with the public IP addresses of your DNS servers.

The registrar submits these hostnames and IP addresses to the registry. The registry publishes them as child nameserver or glue information according to the rules for that domain extension. This prevents a circular lookup when a domain uses a nameserver inside that same domain.

Most domain owners do not need this

Registering private nameservers is different from pointing a domain to Kiravo. To use Kiravo’s assigned nameservers or nameservers from another DNS provider, follow Set nameservers instead.

Before you start

You need:

• A domain managed in the Kiravo client area.
• Nameserver hostnames such as ns1.example.com and ns2.example.com. You should normally provide at least two. Some domain extensions require two or more.
• The public, routable IP address assigned to each authoritative DNS server.
• A working DNS service that answers authoritatively on both UDP and TCP port 53 for every domain you plan to delegate to these nameservers.

For better resilience, place the nameservers on independent servers or networks. Two hostnames that reach the same server do not protect against a server or network outage.

Create matching A or AAAA records for the nameserver hostnames in the authoritative DNS zone. These DNS records and the glue information published by the registry must contain the same addresses. If your DNS server does not have working IPv6 connectivity, do not register IPv6 glue or publish an AAAA record for it. Doing so can cause DNS resolution failures for IPv6-only clients.

The exact requirements can vary by domain extension. Check the registry’s rules or ask support before registering the hostnames if you are unsure about the required number of nameservers or the accepted IP versions.

Configure the DNS servers first

This form only registers the nameserver hostname and its IP address with the domain registry. It does not install DNS software, create a DNS zone, or make the server authoritative. Delegating domains before the DNS servers are ready can take their websites and email offline.

Register a private nameserver

1. Sign in to the Kiravo client area.
2. Open Services → Domains and select the domain that will contain the nameserver hostname.
3. On Domain details, check the domain name and open Register Nameservers.
4. Enter the host part of the nameserver name, such as ns1. The form adds the domain suffix automatically.
5. Enter the public address of that DNS server in IP Address.
6. Check the resulting hostname and IP address, then click Save Changes.
7. Repeat the process for each additional nameserver. Use the hostname and IP address assigned to that server.
8. Confirm that every registered nameserver appears in the list on the same page.

Use the registered nameservers

Wait until the authoritative DNS servers answer correctly for the domain you want to delegate. Then follow Set nameservers and enter the private nameserver hostnames as custom nameservers.

Registering ns1.example.com does not automatically assign it to example.com or to any other domain. Registration and delegation are separate changes.

Change or remove a registration

Open Register Nameservers for the parent domain and find the existing entry. If the page offers an action for the entry, use it to update the IP address or remove the registration.

Before changing an address, update the DNS service and the matching A or AAAA record. Keep the old server available while DNS caches expire when possible.

A registry or registrar may prevent removal while delegated domains still reference the nameserver. Move those domains to other nameservers first if required. If the entry has no change or removal action, open a support ticket with the parent domain, nameserver hostname, and intended IP address. Do not include server passwords or access keys.

After any change, check the registered hostname through a public RDAP or WHOIS lookup and test that the authoritative server answers for the delegated zones.