Becoming a Registrar

DigiNøltar operates a deliberately streamlined registrar model. Parties that are delegated a top-level domain (TLD) within the DigiNøltar root assume the role of registrar for that entire namespace. In order to start the application process please open an issue on our codeberg repo.

Technical Requirements

To operate a TLD, the following is required:

• A publicly reachable IP address
• A DNS service available on port 53
• An authoritative DNS server capable of serving your TLD

Once delegation has been completed, full administrative control over the TLD is transferred to the registrar.

Registrar Responsibilities

While DigiNøltar maintains a minimal policy framework, one expectation is central:

Registrars are expected to make domains available to third parties upon request, provided the requested domain is not already allocated or reserved.

No specific automation, provisioning systems, or interfaces are required. Domain allocation may be handled through direct communication channels.

Administrative Procedures

DigiNøltar does not prescribe how registrars manage requests. Acceptable methods include, but are not limited to:

• Direct messaging platforms
• Electronic mail or federated messaging systems

Registrars may also implement more structured procedures where desired. These may include:

• Formal request forms requiring signatures
• Fax-based submission processes
• Physical delivery via postal systems such as Øl Post or Chaos Post

Registrars are encouraged to define procedures appropriate to their operational model.

Operational Considerations

Registrars should be aware of the following:

• If the authoritative DNS server for your TLD becomes unavailable, new queries may not be resolved
• Previously resolved records may continue to function due to caching by DigiNøltar
• Availability and performance of the TLD are dependent on the registrar’s infrastructure

DigiNøltar does not actively manage or intervene in registrar operations.

Delegating Your TLD

Following approval, your TLD will be delegated to your authoritative DNS server.

DigiNøltar will assign a hostname within the *.gtld-servers.ol namespace (e.g. ns1.yourtld.gtld-servers.ol.) pointing to your server. This hostname must be used as the authoritative nameserver for your TLD.

Setting up a DNS server

Install an authoritative DNS server such as PowerDNS, NSD or BIND.

Create a zone file containing at minimum:

• A valid SOA (Start of Authority) record
• At least one NS record

Afterwards, you can delegate domains! As registrar, you can:

• Host domain records directly on your own authoritative DNS server, or
• Delegate domains to external nameservers (when someone asks for a domain)

Example Zone Configuration

yourtld.zone:

$ORIGIN yourtld.
$TTL 3600
@ IN SOA ns1.yourtld.gtld-servers.ol. hostmaster.yourtld. 1775731518 3600 60 604800 60
@ IN NS ns1.yourtld.gtld-servers.ol.

; example.yourtld
example IN NS ns1.yourtld.gtld-servers.ol.

example.yourtld.zone:

$ORIGIN example.yourtld.
$TTL 3600
@ IN SOA ns1.yourtld.gtld-servers.ol. hostmaster.yourtld. 1775731518 3600 60 604800 60
@ IN NS ns1.yourtld.gtld-servers.ol.

@ IN A 123.123.123.123

For more example zonefiles using DigiNøltar infrasturcture, reference the open source DigiNøltar configuration files on Codeberg.

Future Developments

DigiNøltar is currently developing a managed authoritative DNS service. This will allow registrars to operate TLDs without maintaining their own infrastructure, while retaining full control over delegation and policy.

Further information will be made available in due course.

DigiNøltar is committed to providing a structured, accessible framework for operating top-level domains, while minimizing unnecessary complexity.