DNS: Difference between revisions

From 44Net Wiki
No edit summary
mw push
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{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.  
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:
A typical DNS path on 44Net:
Line 28: Line 28:


* [[DNS/Overview|DNS Overview and Concepts]]
* [[DNS/Overview|DNS Overview and Concepts]]
== Older docs and notes ==
Earlier pages that may still be useful:
* [[Verification]]
* See [[Archive]] for more.

Latest revision as of 00:24, 27 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.


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: