DNS: Difference between revisions

From 44Net Wiki
Updating DNS section landing page with a summary and links to sub-pages // via Wikitext Extension for VSCode
→‎What You Can Manage: maybe don't wade into DS/DNSKEY here yet
Line 17: Line 17:
* Subdomains under ''ampr.org'' (for example ''ki5qkx.ampr.org'').
* Subdomains under ''ampr.org'' (for example ''ki5qkx.ampr.org'').
* Records beneath your subdomain (for example ''houston.ki5qkx.ampr.org'').
* Records beneath your subdomain (for example ''houston.ki5qkx.ampr.org'').
* Delegation via ''NS'' records (and optional ''DS''/''DNSKEY'').
* Delegation via ''NS'' records


== Supported Record Types ==
== Supported Record Types ==

Revision as of 21:55, 4 February 2026

DNS in the 44Net Portal

This page explains how the Portal provides DNS, what you can manage, and where to find step-by-step instructions.

What the Portal Provides

  • User-managed subdomains under ampr.org (typically your callsign).
  • A web interface for creating and managing DNS resource records.
  • Optional delegation to your own authoritative name servers.
  • Hourly export of DNS data to the authoritative servers.

Requirements

  • You must have a Portal account.
  • Callsign-based subdomains require a verified amateur radio callsign.
  • Requests that do not match a verified callsign require staff review.

What You Can Manage

  • Subdomains under ampr.org (for example ki5qkx.ampr.org).
  • Records beneath your subdomain (for example houston.ki5qkx.ampr.org).
  • Delegation via NS records

Supported Record Types

Common Types:

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • SRV

Advanced Types:

  • CAA
  • LOC
  • RP
  • PTR
  • NS
  • DNSKEY
  • DS

Update Schedule

DNS changes are exported on an hourly schedule. Expect up to about one hour for updates to reach the authoritative servers, plus any resolver caching based on TTL.

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.

DNSSEC Status

DNSSEC is a zone-wide feature that must be enabled at the ampr.org apex. It is not something individual users can turn on for their subdomains in the Portal. Currently, DNSSEC is not enabled for ampr.org. We expect to implement it in the future. When it is enabled, records managed directly in the Portal will automatically benefit from DNSSEC at the parent zone.

How-To Guides