DNS: Difference between revisions

From 44Net Wiki
→‎What You Can Manage: maybe don't wade into DS/DNSKEY here yet
mw push
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
= DNS in the 44Net Portal =
{{DISPLAYTITLE:44Net DNS}}
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.
A typical DNS path on 44Net:
# Claim a callsign-based subdomain under ampr.org.
# Create DNS records that map hostnames to IP addresses.


== What the Portal Provides ==
This is sufficient for publishing things like web servers, gateways, remote stations, and repeaters.
* 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 ==
* [[DNS/Portal/Subdomains|Claiming a Subdomain]]
* You must have a Portal account.
* [[DNS/Portal/Records|Managing Records]]
* Callsign-based subdomains require a verified amateur radio callsign.
* Requests that do not match a verified callsign require staff review.


== What You Can Manage ==
== Running your own DNS ==
* 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 ==
Some participants run their own DNS servers rather than relying only on the Portal.
Common Types:
* A
* AAAA
* CNAME
* MX
* TXT
* SRV


Advanced Types:
In this approach, control of a domain is delegated to local systems, while remaining part of the ampr.org domain.
* CAA
* LOC
* RP
* PTR
* NS
* DNSKEY
* DS


== Update Schedule ==
This supports automation, custom workflows, and closer integration with locally managed services.
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) ==
* [[DNS/Portal/Delegations|Delegating DNS to an Independent Name Server]]
Reverse DNS delegation is available for eligible IPv4 subnets between /16 and /24. This is currently a manual process:
* [[DNS/Setup/OpenBSD_Resolver|Setting up a Recursive Resolver on OpenBSD]]
* 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.
== Understanding DNS ==


== DNSSEC Status ==
For background on how DNS works (with 44Net use in mind):
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/Overview|DNS Overview and Concepts]]
* [[ampr-subdomain-claim|Claim your callsign subdomain]]
 
* [[ampr-subdomain-records|Add DNS records to your subdomain]]
== Older docs and notes ==
* [[ampr-subdomain-delegation|Delegate your subdomain to your own name servers]]
Earlier pages that may still be useful:
* [[Verification]]
* See [[Archive]] for more.
[[Category:Explanation]]
[[Category:DNS]]

Latest revision as of 18:53, 30 April 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.

A typical DNS path on 44Net:

  1. Claim a callsign-based subdomain under ampr.org.
  2. 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):

Older docs and notes

Earlier pages that may still be useful: