DNS/Portal/Delegations

From 44Net Wiki
Revision as of 22:15, 4 February 2026 by KI5QKX (talk | contribs) (Add link back)

← Back to DNS

Delegate Your Subdomain to Your Own Name Servers

This guide explains how to point your subdomain (for example ki5qkx.ampr.org) at your own authoritative DNS servers.

When to Delegate

Delegate if you want to manage the entire zone yourself (custom SOA, advanced records, automated DNS, etc.). If you only need a few records, it is simpler to manage them directly in the Portal.

Add NS Records

  1. Go to DNSMy subdomains.
  2. Open your subdomain and choose Add a resource record.
  3. Select record type NS.
  4. For the hostname, use @ to delegate the subdomain apex (ki5qkx.ampr.org).
  5. For the nameserver value, enter a fully qualified domain name and include a trailing period.
    • Example: ns1.example.net.
  1. Create at least two NS records, one per nameserver.

Glue (When Needed)

If your nameserver hostnames are inside the delegated zone (for example ns1.ki5qkx.ampr.org), you must also add A/AAAA records for those hostnames in the Portal so resolvers can reach them.

SOA Responsibility

After delegation, your own nameservers are responsible for the zone's SOA record and all records beneath it. The Portal only needs the NS (and any glue) to delegate the zone.

DNSSEC (Optional)

If you sign your zone, add DS (and/or DNSKEY if required) records for the delegated zone using the record forms in the Portal.

Update Timing

The Portal runs DNS export jobs on an hourly schedule (including address record sync). Expect up to about one hour for changes to reach the DNS servers, plus any TTL caching time on resolvers.