Latest revision as of 22:18, 4 February 2026

← 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

Go to DNS → My subdomains.
Open your subdomain and choose Add a resource record.
Select record type NS.
For the hostname, use @ to delegate the subdomain apex (ki5qkx.ampr.org).
For the nameserver value, enter a fully qualified domain name and include a trailing period.

- Example: ns1.example.net.

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.

Reverse DNS (rDNS)

Reverse DNS delegation is available for eligible IPv4 subnets between /16 and /24. This is currently a manual process:

Open a Portal ticket.
Include the subnet and the authoritative name servers you want to use.
Staff will review and delegate rDNS if approved.

This will be automated in the Portal in the future.

@@ Line 1: / Line 1: @@
+{{Section nav
+ | hub=DNS
+ | title=DNS
+ | category=DNS
+}}
 = Delegate Your Subdomain to Your Own Name Servers =
@@ Line 21: / Line 27: @@
 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) ==
+== Reverse DNS (rDNS) ==
-If you sign your zone, add ''DS'' (and/or ''DNSKEY'' if required) records for the delegated zone using the record forms in the Portal.
+Reverse DNS delegation is available for eligible IPv4 subnets between /16 and /24. This is currently a manual process:
+* Open a Portal ticket.
+* Include the subnet and the authoritative name servers you want to use.
+* Staff will review and delegate rDNS if approved.
-== Update Timing ==
+This will be automated in the Portal in the future.
-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.