DNS: Difference between revisions

Revision as of 00:04, 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.

This page outlines the common ways people use DNS on 44Net and links to more detailed documentation.

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: @@
-Net's DNS service provides name resolution and delegation
+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.
-for hosts on 44Net. This section documents how DNS
-is operated on 44Net, how participants can manage their own records in the Portal, and
-how to set up a local DNS server.
-== Using DNS via the Portal ==
+This page outlines the common ways people use DNS on 44Net and links to more detailed documentation.
-The [https://portal.ampr.org/|44Net Portal] provides a web interface for managing subdomains,
-records, and delegations.
-* [[DNS/Portal|DNS in the 44Net Portal]]
+== Getting Started ==
-* [[DNS/Portal/Subdomains|Managing Subdomains]]
+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.
+* [[DNS/Portal/Subdomains|Claiming a Subdomain]]
 * [[DNS/Portal/Records|Managing Records]]
-* [[DNS/Portal/Delegations|Delegating DNS to your own name servers]]
 == Running Your Own DNS ==
-Participants may operate their own resolvers and authoritative servers.
+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.
+* [[DNS/Portal/Delegations|Delegating DNS to an Independent Name Server]]
 * [[DNS/Setup/OpenBSD_Resolver|Setting up a Recursive Resolver on OpenBSD]]
-== What is DNS? ==
+== Understanding DNS ==
+For background on how DNS works (with 44Net use in mind):
 * [[DNS/Overview|DNS Overview and Concepts]]