DNS: Difference between revisions
Add link to new openbsd page |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
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. | |||
* [[DNS/Portal/Subdomains|Claiming a Subdomain]] | |||
* Subdomains | * [[DNS/Portal/Records|Managing Records]] | ||
* Records | |||
== | == 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. | |||
* [[DNS/Portal/Delegations|Delegating DNS to an Independent Name Server]] | |||
* [[DNS/Setup/OpenBSD_Resolver|Setting up a Recursive Resolver on OpenBSD]] | |||
== | == Understanding DNS == | ||
For background on how DNS works (with 44Net use in mind): | |||
* [[DNS/ | |||
* [[DNS/Overview|DNS Overview and Concepts]] | |||
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):