ba51c78a9ea70b7d06d0d102b71c036a2d63fa76
services/Clearnet-Domains.md
| ... | ... | @@ -0,0 +1,25 @@ |
| 1 | +# DN42 Clearnet Domains |
|
| 2 | + |
|
| 3 | +To provide services over the public internet some community members have contributed public internet domain names to be used for DN42. |
|
| 4 | + |
|
| 5 | +|Domain| |
|
| 6 | +|:--| |
|
| 7 | +|dn42.dev| |
|
| 8 | +|dn42.no| |
|
| 9 | + |
|
| 10 | +DNS records for these domains are managed by a gitea repository: |
|
| 11 | + |
|
| 12 | +- [https://git.dn42.dev/dns/clearnet](https://git.dn42.dev/dns/clearnet) |
|
| 13 | + |
|
| 14 | +The repository uses the registry drone CI service and [DNSControl](https://stackexchange.github.io/dnscontrol/) to automatically build and push changes. This provides a degree of independence for the domains and allows them to be updated by any of the registry maintainers. |
|
| 15 | + |
|
| 16 | +## Requesting Changes |
|
| 17 | + |
|
| 18 | +If you have a public DN42 service or a DN42 related domain that you'd like to add, simply submit a PR to the [repository](https://git.dn42.dev/dns/clearnet). |
|
| 19 | + |
|
| 20 | +Domains and services should meet the following criteria: |
|
| 21 | + |
|
| 22 | +- Services and DNS should be resilient and highly available, where possible |
|
| 23 | +- The owner must ensure their contact details are current and respond promptly to any failures |
|
| 24 | +- If a domain or service is unavailable for a length of time, it may be removed |
|
| 25 | + |