• Home

  • Getting Started
  • Registry Authentication
  • Address Space
  • BGP communities
  • FAQ

• How-To

  • Wireguard
  • Openvpn
  • IPsec With Public Keys
  • Tinc
  • GRE on FreeBSD
  • GRE on OpenBSD
  • IPv6 Multicast (PIM-SM)
  • SSM Multicast
  • MPLS
  • Bird2
  • FRRouting
  • OpenBGPD
  • Mikrotik RouterOS
  • EdgeRouter
  • Static routes on Windows
  • Universal Network Requirements
  • VyOS
  • NixOS

• Services

  • IRC
  • Whois registry
  • DNS
  • IX Collection
  • Public DNS
  • Looking Glasses
  • Automatic Peering
  • Repository Mirrors
  • Distributed Wiki
  • Certificate Authority
  • Route Collector
  • Registry

• Internal

  • Internal services
  • Interconnections
  • APIs
  • Show and Tell
    
  • Historical services

• Historical

  • Bird 1
  • Quagga

• External Tools

  • Paste Board
  • Git Repositories

DN42 Clearnet Domains

To provide services over the public internet some community members have contributed clearnet domain names to be used for DN42.

DNS records for these domains are managed by a gitea repository:

• https://git.dn42.dev/dns/clearnet

The repository uses the registry drone CI service and 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.

Requesting Changes

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.

Domains and services should meet the following criteria:

• Services and DNS should be resilient and highly available, where possible
• The owner must ensure their contact details are current and respond promptly to any failures
• If a domain or service is unavailable for a length of time, it may be removed

Hosted by: BURBLE-MNT, GRMML-MNT, XUU-MNT, JAN-MNT, LARE-MNT, SARU-MNT, ANDROW-MNT, MARK22K-MNT | Accessible via: dn42, dn42.dev, dn42.eu, wiki.dn42.us, dn42.de (IPv6-only), dn42.cc (wiki-ng), dn42.wiki, dn42.pp.ua, dn42.obl.ong