DNS/Portal/Delegations - Revision history

KI5QKX: mw push

2026-04-30T18:52:36Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 34:		Line 34:

	This will be automated in the Portal in the future.		This will be automated in the Portal in the future.
			[[Category:Reference]]
	[[Category:DNS]]		[[Category:DNS]]
	[[Category:DNS Portal]]		[[Category:DNS Portal]]
	[[Category:Portal]]		[[Category:Portal]]

KI5QKX: mw push

2026-03-01T00:14:30Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 34:		Line 34:

	This will be automated in the Portal in the future.		This will be automated in the Portal in the future.
			[[Category:DNS]]
			[[Category:DNS Portal]]
			[[Category:Portal]]

KI5QKX: mw push

2026-02-28T23:20:17Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 9:		Line 9:
	This guide explains how to point your subdomain (for example ''ki5qkx.ampr.org'') at your own authoritative DNS servers.		This guide explains how to point your subdomain (for example ''ki5qkx.ampr.org'') at your own authoritative DNS servers.

	== When to ~~Delegate~~ ==		== 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.		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~~ ==		== Add NS records ==
	# Go to ''DNS'' → ''My subdomains''.		# Go to ''DNS'' → ''My subdomains''.
	# Open your subdomain and choose ''Add a resource record''.		# Open your subdomain and choose ''Add a resource record''.
Line 21:		Line 21:
	# Create at least two NS records, one per nameserver.		# Create at least two NS records, one per nameserver.

	== Glue (~~When Needed~~) ==		== 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.		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~~ ==		== 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.		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.

KI5QKX: Moving rDNS to Delegations

2026-02-04T22:18:05Z

Moving rDNS to Delegations

← Older revision		Revision as of 22:18, 4 February 2026
Line 27:		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.		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~~.

KI5QKX: Add link back

2026-02-04T22:15:15Z

Add link back

← Older revision		Revision as of 22:15, 4 February 2026
Line 1:		Line 1:
			{{Section nav
			\| hub=DNS
			\| title=DNS
			\| category=DNS
			}}

	= Delegate Your Subdomain to Your Own Name Servers =		= Delegate Your Subdomain to Your Own Name Servers =

KI5QKX: Adding a rDNS delegation stub page // via Wikitext Extension for VSCode

2026-02-04T21:54:18Z

Adding a rDNS delegation stub page // via Wikitext Extension for VSCode

New page

= 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.

== 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.