DNS Quickstart

To use FibaCloud for authoritative DNS, first confirm that your account has an active DNS service. Open DNS Management in the control panel. In the account checked on 30 October 2026, the menu showed zero DNS services and this link returned to the dashboard; no zone-creation form or assigned name servers were available in that account.

Set Up Domains

1. Confirm DNS service availability and the applicable domain limits. If no DNS management controls appear, ask support about activation before changing your domain's delegation.
2. Collect the domain's existing DNS records and note which provider currently hosts the zone.
3. With an active service, add the domain and recreate the records your services require.
4. Obtain the authoritative name-server hostnames assigned to that DNS service and verify that they answer for your zone.
5. Change the domain's name servers at your registrar only after the new zone is ready.

Creating a DNS zone does not register a domain or change its delegation at the registrar.

Point to FibaCloud Name Servers From Common Domain Registrars

Your registrar manages the domain's delegation. The DNS provider hosts the zone and answers queries for its records. Use the name-server settings in your registrar's current interface or instructions.

Prerequisites

You need control of the domain, access to its registrar, a working DNS service and a copy of the required records. Keep the previous DNS service available while you verify the change.

Instructions

Use the exact authoritative name-server hostnames supplied for your active DNS service. If they are not shown, confirm them with support before saving a change at the registrar.

You can inspect DNS answers with commands such as:

dig NS example.com +short
dig @ns1.example.net example.com SOA

Replace example.com with your domain and ns1.example.net with an assigned authoritative name server. Check that the new servers answer for the zone and that its required records are present. Then update the registrar's name-server settings and check the delegation again.

Summary

A name-server change updates the domain's delegation through its registrar and registry. Recursive DNS resolvers may continue using cached delegation and record data until the relevant TTLs expire. There is no fixed propagation duration: compare authoritative answers and the resolvers used by your visitors while the change takes effect.

What is Next?

Create and manage DNS records, then verify the hostname, application response and HTTPS certificate for the services you publish.