OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Infrastructure

Ncdns

Ncdns is a Go daemon that retrieves zone data from a Namecoin node over JSON-RPC and serves it through DNS as an authoritative nameserver. It can optionally sign zones with DNSSEC and supports Namecoin DS records.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Ncdns — OpenViST project profile in Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use ncdns when you need a DNS nameserver to retrieve Namecoin zone data from a Namecoin node and serve it to a recursive resolver or stub-zone configuration.

Who it is for

  • Operators configuring DNS resolution for Namecoin names.
  • Administrators integrating Namecoin zones with Unbound or another recursive resolver.
  • Developers building or adapting Namecoin-to-DNS infrastructure.

Documented uses

  • Serve Namecoin zone records through an authoritative nameserver.
  • Connect a recursive resolver to Namecoin zone data through a stub-zone setup.
  • Optionally sign served zones with DNSSEC and provide a KSK trust anchor to Unbound.
  • Serve names containing a “bit” label with an alternate suffix.
Before you choose

Requirements & limits

The project is available as a public GitHub repository under the GPL-3.0 license.

  • A Namecoin node with JSON-RPC enabled is required, and ncdns needs the interface address and any required credentials.
  • The README recommends pairing ncdns with Unbound or another recursive resolver, or using it as an authoritative nameserver for a stub zone.
  • DNSSEC requires generating a KSK and ZSK; for Unbound validation, the KSK public key is configured as a trust anchor.
  • Serving alternate suffixes can change the hostname transmitted by HTTP and may require web-server configuration changes.
  • The README documents a Go modules build path for Go 1.15 or later; Linux also requires libcap development headers.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build ncdns with Go modules

Build the ncdns binaries from a local source checkout using the README's Go modules procedure.

Before you start

  • Go 1.15 or later
  • Bash
  • A local clone of the ncdns repository
  • On Linux, libcap development headers

Steps

  1. Clone the ncdns repository.

  2. In the repository directory, run the command below.

    Documented command
    go mod init github.com/namecoin/ncdns

  3. Run the command below.

    Documented command
    go mod edit -replace github.com/coreos/go-systemd=github.com/coreos/go-systemd/v22@latest

  4. Run the command below, then the command below.

    Documented command
    go mod tidy
    Documented command
    go install ./...

Expected outcome

The README says the binaries are built in `$GOPATH/bin/ncdns`.

Guide limitations

  • The instructions specify Bash and Go 1.15 or later.
  • Linux builds require libcap development headers.
Documentation 1 ↗
Source-based practical guide

Configure DNSSEC keys for an Unbound trust anchor

Generate ncdns DNSSEC signing keys and configure the KSK public key as an Unbound trust anchor.

Before you start

  • A configured ncdns deployment
  • The dnssec-keygen or ldns-keygen utility
  • Unbound, if configuring a resolver trust anchor

Steps

  1. Generate a key-signing key with dnssec-keygen -a RSASHA256 -3 -b 2048 -f KSK bit.

  2. Generate a zone-signing key with dnssec-keygen -a RSASHA256 -3 -b 2048 bit.

  3. Identify the KSK public .key file and configure ncdns to use the DNSSEC keys.

  4. For Unbound, add the KSK public key file as a trust-anchor-file under its server configuration.

Expected outcome

The documented configuration makes the KSK public key available to Unbound as a trust anchor for the ncdns-signed zone.

Guide limitations

  • DNSSEC is optional.
  • The README notes that bit should be used as the key name when the key is intended as an Unbound trust anchor.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
11 October 2026
Original website title
namecoin/ncdns · Official homepage title · retained in its source language
How we review sourcesSuggest a correction