Skip to the page
KilbyDocs
Build and run View as Markdown
On this page

DNS AI

DNS AI hosts your domain's whole DNS zone on Kilby: the records of your site, your email and anything else. You edit them in the dashboard or the API, and Kilby publishes every change to its name servers within a minute.

Move a domain to Kilby#

  1. Add the domain under DNS AI in the sidebar: the whole domain, as you bought it (example.com, not www.example.com). If the domain's registrar already uses name servers of a zone Kilby hosts, Kilby does not make a second, empty one: when no workspace holds that zone, a Kilby admin can attach it to your workspace with the records it has today.
  2. Prove the domain is yours. At the DNS provider the domain uses today, create one TXT record: the name _kilby-challenge (in full, _kilby-challenge.example.com) with the value the page shows, kilby-verify= and a token of this request. Kilby looks for it at the name servers the registry lists for the domain, never through a cache: every 2 minutes for the first hour, then every hour, and at once when you click Verify now. Only when it answers does Kilby create the zone and give it four name servers. A request that is never proven is removed after 7 days. Nothing changes for your visitors: the registry still sends them to your current DNS provider. You can delete the TXT record once the zone exists.
  3. Capture what the domain answers today. Kilby asks the name servers the domain uses now about every record a source suggests, and keeps only what they really answer, with the values they answer:
    • Scan looks at the names most domains use: the site, mail (MX, SPF, DMARC, MTA-STS), the signing keys (DKIM) of well-known mail services and Microsoft 365's records.
    • Zone file: paste the zone your current provider exports. It is the only way to bring names no scan can guess, such as some signing keys and verifications.
    • Kilby AI (when Kilby AI is on for this platform): paste what your provider's panel shows, or upload one screenshot of it (PNG or JPEG, at most 4 MB), or leave both empty and it checks the domain's public DNS for records a scan may miss. It only suggests, and Kilby checks each record like the others. It has its own consent, asked of an owner or admin the first time: see Kilby AI for exactly what it sends. Add what was captured to the zone with one click.
  4. Make sure nothing is missing. Kilby asks its own name servers, which answer for the zone before the move, about every captured record. Moving the name servers stays blocked while a record is missing, unless you mark it as not wanted.
  5. Give your registrar the four name servers (where you bought the domain: NIC Chile for a .cl domain, GoDaddy, Namecheap…), replacing all the current ones. Kilby asks the registry of the domain's top-level domain directly, not a cache, and shows the zone as Active once it delegates to exactly those four.

Only workspace admins add domains and change records, because one change can stop a domain's email. Everyone in the workspace can see them.

Records#

The editor takes A, AAAA, CNAME, MX, TXT, CAA and SRV records, and ALIAS: a record that points to Kilby's load balancer and, unlike a CNAME, works on the domain itself (example.com). Each record set has a name relative to the zone (@ for the domain itself, www, _dmarc), one or more values, and a TTL from 60 seconds to a day.

Kilby refuses what DNS does not allow: a CNAME on the domain itself, or next to another record of the same name. A TXT value longer than 255 characters is split as DNS requires. Every save is a new version in the zone's History, with who made it; any earlier version can be restored.

Point a service at Kilby#

When a custom domain of a service is inside an active zone, its Domains tab and the zone page offer Configure automatically. Kilby then adds, in one step, an ALIAS to its load balancer at the domain's name and the _acme-challenge record that gets its certificate. Those records are kept by Kilby for the domain: they cannot be edited by hand, and they go when the domain goes. Records of the site that were at that name (A, AAAA, CNAME) are replaced; mail records are left alone.

DNSSEC#

If DNSSEC is on at your registrar (it holds a DS record for the domain), moving the name servers would stop the domain from resolving for everyone whose resolver checks signatures, because Kilby does not sign zones yet. The zone shows it, and moving stays blocked: turn DNSSEC off at the registrar first.

Deleting a zone#

Deleting a zone removes its records at once. The zone itself stays, empty, for as long as the registrar still uses its name servers, so that nobody else can take the domain over; Kilby removes it as soon as the registrar points elsewhere. A zone whose name servers were never used is removed after 7 days. A domain that was never proven has nothing in DNS yet, so deleting it removes the request at once.

Limits#

The number of domains a workspace can host depends on its plan: 1 on Hobby, 10 on Pro and 50 on Scale. A zone waiting for its name servers counts too. During the beta, every workspace can host 10.

API#

The same operations are in the API reference: list, create and delete zones, put and delete record sets, capture, and configure a custom domain.

  • Custom domains: attach a domain to a service, and what to create at a DNS provider that is not Kilby.
  • Limits: what each plan includes.
  • API reference: the DNS AI endpoints.