Pointing your registrar at KumoDNS

Once the zone exists here and its records are right, you change the delegation at your registrar.

Use all four nameservers

ns01.kumodns.com
ns02.kumodns.com
ns03.kumodns.com
ns04.kumodns.com

Enter all four. Any one of them can answer for your domain, so losing a region does not take your DNS with it — and our availability commitment is measured on exactly that basis: a minute only counts against us when all four fail to answer. Delegating to fewer removes the redundancy you are paying for.

A nameserver name is a delegation target, not a single machine. Each one can resolve to more than one server, so capacity grows behind a name without you touching your registrar again.

Do it in this order

1. Create the zone in KumoDNS.
2. Add or import every record.
3. Verify with dig @ns01.kumodns.com yourdomain that the answers are right, or use the delegation check if you would rather not use dig.
4. Then change the nameservers at your registrar.

Done this way there is never a moment where the domain is delegated to a zone that does not exist yet.

How long it takes

Two different clocks get confused here.

Our side is immediate. A record you save publishes to all four nameservers in seconds, and the portal shows you when each one has it.

The rest of the internet is not. Resolvers hold the previous answer until its TTL expires, and the registry's own nameserver change can take a couple of hours to propagate. If you know a change is coming, lowering the TTL on the affected records a day beforehand shortens the window — see SOA and TTL.

Do not remove the old provider immediately

Leave the previous zone in place for a few days. If something was missed, the old provider is no longer answering, but the records are still there for you to read.

Last reviewed 2026-09-24.