DNS: Difference between revisions

Latest revision as of 00:05, 5 February 2026

The 44Net DNS service provides name resolution and delegation for 44Net users. Most participants use it to publish hostnames for their systems, starting with a callsign-based subdomain and adding records as needed.

Getting Started

A typical DNS path on 44Net:

Claim a callsign-based subdomain under ampr.org.
Create DNS records that map hostnames to IP addresses.

This is sufficient for publishing things like web servers, gateways, remote stations, and repeaters.

Running Your Own DNS

Some participants run their own DNS servers rather than relying only on the Portal.

In this approach, control of a domain is delegated to local systems, while remaining part of the ampr.org domain.

This supports automation, custom workflows, and closer integration with locally managed services.

Understanding DNS

For background on how DNS works (with 44Net use in mind):

DNS Overview and Concepts

@@ Line 1: / Line 1: @@
-= DNS in the 44Net Portal =
+The 44Net DNS service provides name resolution and delegation for 44Net users. Most participants use it to publish hostnames for their systems, starting with a callsign-based subdomain and adding records as needed.
-This page explains how the Portal provides DNS, what you can manage, and where to find step-by-step instructions.
+== Getting Started ==
-== What the Portal Provides ==
+A typical DNS path on 44Net:
-* User-managed subdomains under ''ampr.org'' (typically your callsign).
+# Claim a callsign-based subdomain under ampr.org.
-* A web interface for creating and managing DNS resource records.
+# Create DNS records that map hostnames to IP addresses.
-* Optional delegation to your own authoritative name servers.
-* Hourly export of DNS data to the authoritative servers.
-== Requirements ==
+This is sufficient for publishing things like web servers, gateways, remote stations, and repeaters.
-* 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 ==
+* [[DNS/Portal/Subdomains|Claiming a Subdomain]]
-* Subdomains under ''ampr.org'' (for example ''ki5qkx.ampr.org'').
+* [[DNS/Portal/Records|Managing Records]]
-* Records beneath your subdomain (for example ''houston.ki5qkx.ampr.org'').
-* Delegation via ''NS'' records
-== Supported Record Types ==
+== Running Your Own DNS ==
-Common Types:
-* A
-* AAAA
-* CNAME
-* MX
-* TXT
-* SRV
-Advanced Types:
+Some participants run their own DNS servers rather than relying only on the Portal.
-* CAA
-* LOC
-* RP
-* PTR
-* NS
-* DNSKEY
-* DS
-== Update Schedule ==
+In this approach, control of a domain is delegated to local systems, while remaining part of the ampr.org domain.
-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.
-== DNSSEC Status ==
+This supports automation, custom workflows, and closer integration with locally managed services.
-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 ==
+* [[DNS/Portal/Delegations|Delegating DNS to an Independent Name Server]]
-* [[DNS/Portal/Subdomains|Claim your callsign subdomain]]
+* [[DNS/Setup/OpenBSD_Resolver|Setting up a Recursive Resolver on OpenBSD]]
-* [[DNS/Portal/Records|Add DNS records to your subdomain]]
-* [[DNS/Portal/Delegations|Delegate your subdomain to your own name servers]]
+== Understanding DNS ==
+For background on how DNS works (with 44Net use in mind):
+* [[DNS/Overview|DNS Overview and Concepts]]