List of public services provided by the burble.dn42 network.


Public Website

burble.dn42 (dn42 link) (public internet link)

This website is built using GRAV and currently hosted on dn42-fr-sbg1. The public internet version is protected by CloudFlare.
Longer term, regional replicas of the DN42 site may be provided however this is not currently configured.

PrivateBin Instance

paste.burble.dn42 (dn42 link) (public internet link)

burble.dn42 PrivateBin instance.

Looking Glass (public internet link)
lg.burble.dn42 (dn42 link)

The burble.dn42 looking glass is based on bird-lg with patches by Zhaofeng, tds and myself to fix formating, bird2 compatibility and other tweaks.

A fork of sileht/bird-lg that includes all of our fixes is available on GitHub.

DN42 registry data in the BGP Map part of the looking glass uses lgregmapper to interface with dn42regsrv.

The looking glass is hosted on fr-sbg1 behind CloudFlare.


Authoritative Service
Recursive Service
DN42 Anycast Service

burble.dn42 provides a local, anycast, authoritative and recursive DNS service.
The DNS Service has it's own page.

DNS over HTTPs (DoH)
DNS over TLS

All services support DNS over HTTPs on port 443, and DNS over TLS on port 843.

DN42 Wiki Mirror

Mirror URLs
wiki.dn42  (editable via DN42)
wiki.burble.dn42  (editable via DN42)  (read-only via public internet)  (read-only via public internet)

burble.dn42 maintains a globally distributed mirror of the DN42 Wiki, and is part of the wiki.dn42 anycast group. The DN42 services (wiki.dn42 and wiki.burble.dn42) are editable, whilst the public internet views ( and are read-only.

Please note that updates to the wiki may take several hours to sync with other mirrors.

The service is provided by regional mirrors fronted by an nginx proxy that is itself anycasted across burble.dn42. The service is fully meshed and will continue to operate as long as at least one proxy and mirror is available. The maximum latency across the network is <80ms.
Mirrors are located in the following locations:

  • dn42-fr-sbg1
  • dn42-ca-bhs2
  • dn42-us-dal1
  • dn42-sg-sin1

Pingable IP address

  • pingable.burble.dn42
  • fd42:4242:2601:ac05::1

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.

Registry API Service and Explorer

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.

A public instance of the API and associated explorer web app is available at the following URLs:

Whois Service

  • whois.burble.dn42
  • fd42:4242:2601:ac43::1

WHOIS service providing data from the DN42 registry.

The source code for the service is available in the burble.dn42 git.

Global Route Collector

The global route collector provides a central bird instance that collects routes from peers across the DN42 network.
All users are invited to join the collector and help provide stats for the network.

The route collector can currently be queried by using ssh to connect a bird shell or via a looking glass.
Additional services and stats are expected to be developed in the future.

ROA Data

Route Origin Authorisation (ROA) tables are generated using dn42regsrv and published to the website for general use.

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).

URL  IPv4/IPv6  Description    Both    DN42 ROA data in JSON format    Both    DN42 ROA data for use with Bird1    IPv4 Only    DN42 ROA data for use with Bird1    IPv6 Only    DN42 ROA data for use with Bird1    Both    DN42 ROA data for use with Bird2    IPv4 Only    DN42 ROA data for use with Bird2    IPv6 Only    DN42 ROA data for use with Bird2

NTP Service

All servers in burble.dn42 are part of the NTP Pool Project and provide a stable, high stratum NTP service using chrony. You can see my pool status in my NTP Pool Profile Page.

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.

Lounge IRC Gateway

lounge.burble.dn42 (dn42 link) (public internet link)

The burble.dn42 IRC web gateway is based on thelounge and is provided for DN42 users to access and lurk on the #dn42 IRC channel hosted at hackint.

Please mail [email protected] for an account.
Note that the service is strictly limited to hackint channels.

Public Git Repository

git.burble.dn42 (dn42 link) (public internet link)

burble.dn42 related code and configuration is mastered on a local git repository before being pushed to other public repositories.

Whilst primarily a restricted service, with the intent of making burble.dn42 configuration and code publically available, user accounts can be created on request. Please mail [email protected] for further details.

DN42 Hosting Service

Contact [email protected] if you have a DN42 service that you would like to host on burble.dn42

Network Status and Reporting

Hosted Grafana Service

https://grafana.burble.dn42 dn42 link public internet link

The hosted grafana service has it's own page here.

DN42 Infrastructure Monitoring

burble.dn42 hosts monitoring and alerting of key DN42 services, see the hosted grafana service for more details.

burble.dn42 status

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. Some public graphs are available on the hosted grafana service.

Syslogs are exported in real time to a central logging node on the internal network.