DNS: Difference between revisions

Revision as of 23:58, 26 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:

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

Revision as of 22:26, 26 February 2026 view source KI5QKX (talk \| contribs) Bureaucrats, Interface administrators, Administrators 662 edits mw push ← Older edit		Revision as of 23:58, 26 February 2026 view source KI5QKX (talk \| contribs) Bureaucrats, Interface administrators, Administrators 662 edits mw push Newer edit →
Line 1:		Line 1:
	{{DISPLAYTITLE\|44Net DNS}}		{{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.