Services provided for use within DN42
The service portal allows you to configure your burble.dn42 services.
The main function of the portal is to set a burble.dn42 password for gaining access to other services.
A public issue log is maintained on the DN42 Registry.
Users are welcome to raise issues or enhancements via the log.
The looking glass is hosted on de-fra1 and the public version is behind CloudFlare.
pingable.burble.dn42 is a single IP address that will respond to ping and traceroute requests across the entire network.
This address may be used for automated reachability or latency tests, however please be considerate and configure a reasonable test frequency.
In all cases, do not set the ping frequency to be higher than once a second.
A speed test service is available in France and Canada.
Note that the service is currently available over IPv6 only at this time.
If the service ends up loading or disrupting the rest of the network then I may end up removing it, so remember this service is provided for your benefit and use responsibly.
Each node in the network is monitored by UptimeRobot with alerts if a node becomes unavailable.
Internally, nodes are measured by netdata which provides a real time view of each node. prometheus is then used to collect and store that data for historical reporting. grafana is used for visualisation.
Syslogs are exported in real time to a central logging node on the internal network.
The burble.dn42 shell service provides shell accounts for dn42 users who
have SSH auth methods in the registry.
See the Shell Accounts page.
burble.dn42 provides a local, anycast, authoritative and recursive DNS service.
The DNS Service has it’s own page.
All services support DNS over HTTPs on port 443, and DNS over TLS on port 843.
dn42regsrv is a REST API for the DN42 registry that provides a bridge between interactive applications and the registry.
As well as the main REST API to the DN42 registry, the server can also generate ROA tables and provides a small web application for exploring registry data.
The JSON output file can be used with gortr
to implement ROA checks via RPKI.
The Bird files can be used directly with Bird to implement ROA checks as detailed in the DN42 Wiki (Bird1 / Bird2).
The OpenBGPD files can be used directly with OpenBGPD to implement ROA checks as details in the DN42 Wiki OpenBGPD
|https://dn42.burble.com/roa/dn42_roa_46.json||Both||DN42 ROA data in JSON format|
|https://dn42.burble.com/roa/dn42_roa_bird1_46.conf||Both||DN42 ROA data for use with Bird1|
|https://dn42.burble.com/roa/dn42_roa_bird1_4.conf||IPv4 Only||DN42 ROA data for use with Bird1|
|https://dn42.burble.com/roa/dn42_roa_bird1_6.conf||IPv6 Only||DN42 ROA data for use with Bird1|
|https://dn42.burble.com/roa/dn42_roa_bird2_46.conf||Both||DN42 ROA data for use with Bird2|
|https://dn42.burble.com/roa/dn42_roa_bird2_4.conf||IPv4 Only||DN42 ROA data for use with Bird2|
|https://dn42.burble.com/roa/dn42_roa_bird2_6.conf||IPv6 Only||DN42 ROA data for use with Bird2|
|https://dn42.burble.com/roa/dn42_roa_obgpd_46.conf||Both||DN42 ROA data for use with OpenBGPD|
|https://dn42.burble.com/roa/dn42_roa_obgpd_4.conf||IPv4 Only||DN42 ROA data for use with OpenBGPD|
|https://dn42.burble.com/roa/dn42_roa_obgpd_6.conf||IPv6 Only||DN42 ROA data for use with OpenBGPD|
ROA data is cached via Cloudflare to provide fast local access, and an n8n script is used to update ROA data immediately following registry changes.
burble.dn42 related code and configuration is maintained in a local gitea repository.
burble.dn42 PrivateBin instance.
All servers in burble.dn42 provide a stable, high stratum NTP service using chrony.
The NTP service is exposed over DN42, and users are welcome to use any server in the burble.dn42 network as an NTP time server on either the public or DN42 networks.