DNS server (NanumDNS) — your domain's address book on this device
The NanumOS server edition answers for your own domain (say example.com). When a computer anywhere asks "where is www.example.com?", this device's dnsd answers.
What it is
dnsd reads the right line to whoever asks. Your own server does this, nobody outside. dnsd answers only for your own domains. It never looks up other people's names for anyone (no recursion), so nobody can use it to attack others.
Now: the three steps under "How to use it" make your domain answer from this device. Asking the assistant "put my domain's DNS on this server" does the same.
How to use it
1. Make the domain
The assistant does it, or in a terminal:
2. Turn it on (a service)
The server edition already has the dns service file, but it is off (it does not start before there is a configuration). After making the configuration:
service dns start
3. Add, change and delete names
Adding works at once. **Changing and deleting need --ok**: the assistant first shows a card ("change what into what?") and adds --ok only after the person pressed [Allow]. Every action returns what the server really answers afterwards (asked, not assumed) and how to undo it.
You can edit the file by hand too (BIND and Knot zone files as they are). Raise the SOA serial at the top afterwards (dnsd act serial-bump --json '{"zone":"example.com"}') and the server answers with the new content within a second. A file with a wrong line is not taken: the old content keeps answering, and dnsd doctor says which line and why.
4. Two servers (primary and secondary)
DNS is usually answered by two servers with the same content. The primary's configuration names the secondary, the secondary's names the primary, and both hold the same secret key (TSIG).
A change on the primary is announced to the secondary at once (NOTIFY), and the secondary fetches only what changed (IXFR). The other side may be BIND or Knot.
5. DNSSEC (signing)
Put the DS line it prints into your registrar's DNSSEC field and add dnssec=keys to the zone's line in the printed on a screen or in a log.
How it works
One question goes like this:
- A question packet arrives (UDP port 53). dnsd first checks its shape strictly: a name's shortcut (a compression pointer) may only point backwards, and if any length or count is off, the answer is "format error" and that is all.
- If the name is inside your domain, dnsd looks it up in a table kept sorted in memory. No such name: "no such name" with the SOA; the name exists but not that type: "no such type". Lines starting with
*.(wildcards) answer for names that do not exist. - If the answer is bigger than 512 bytes (1232 for questions with EDNS), only a "truncated" mark goes back, and the asker asks again over TCP and gets all of it.
- When the same place asks the same question more than 20 times a second, the answers are cut down (RRL). This stops attackers from faking someone else's address and using our server to amplify an attack.
When you edit a zone file, the new content is read whole and swapped in only when every check passes, so an edit in progress or a broken file never leaves the answers empty. If the primary goes down while a secondary is fetching, the secondary keeps answering with what it had, and writes only a complete copy to disk (never a half-written file).
Not yet
- NSEC3 (another way of signing): it signs with NSEC today.
- Dynamic updates (DNS UPDATE), DNAME, one address in many places of the world (anycast).
Technical details
- Configuration lines:
listen ADDR:PORT …,key NAME FILE,rrl RATE [SLIP](RATE = answers per second) (0 = off, default 20 2),edns-size 512-4096(default 1232),max-records N,state FILE,zone NAME file=… [primary=ADDR] [key=NAME] [notify=ADDR,…] [transfer=ADDR[/LEN],…] [allow-notify=…] [dnssec=KEYDIR]. - Actions (act):
zonesrecordsrecord-addrecord-change(approval)record-delete(approval)serial-bumpreloadcheck(the file against every answer of the server)zone-addzone-remove(approval)doctor. One JSON line{ok, did, state_after, undo, why}. Whether approval is needed (needs_ok) is decided by a table in the code. - Check:
dnsd doctor— dnsd running, zones loaded (a refused file with its line number), the serials of primary and secondaries the same, days until the signatures expire, as 정상/주의/위험 (fine / caution / danger). State file/tmp/dnsd-UID/state. The assistant'sos_checkhas a 「DNS 서버」 row. - Signing: ECDSA P-256 / SHA-256 (algorithm 13), NSEC, signed again every week (14 to 21 days of validity); the same content gives the same signature (RFC 6979), so only changed lines travel to secondaries. Key rollover follows the Publish/Activate/ Inactive/Delete dates of BIND key files (contract DNSD.md).
- Protocol: UDP and TCP 53, EDNS0, TC and the TCP retry, name compression (backwards only), case kept, ANY answered with one set (RFC 8482), RRL, AXFR/IXFR/NOTIFY, TSIG hmac-sha256.
NanumOS 0.1.8349 · 2026-11-16