--- title: Services visible: true --- List of public services provided by the burble.dn42 network. === #Services ## Public Website [burble.dn42](http://burble.dn42/) (dn42 link) [dn42.burble.com](https://dn42.burble.com/) (public internet link) This website is built using [GRAV](https://getgrav.org/) and currently hosted on dn42-fr-rbx1. The public internet version is protected by [CloudFlare](https://www.cloudflare.com). Longer term, regional replicas of the DN42 site may be provided however this is not currently configured. ## Looking Glass [lg.burble.com](https://lg.burble.com) (public internet link) [lg.burble.dn42](https://lg.burble.dn42) (dn42 link) The burble.dn42 looking glass is based on [bird-lg](https://github.com/sileht/bird-lg) with patches by [Zhaofeng](https://github.com/zhaofengli/bird-lg), [tds](https://github.com/TimStallard/bird-lg) and [myself](https://github.com/sesa-me/bird-lg) to fix formating, bird2 compatibility and other tweaks. A fork of sileht/bird-lg that includes all of our fixes is available on [GitHub](https://github.com/sesa-me/bird-lg). DN42 registry data in the BGP Map part of the looking glass uses [lgregmapper](https://git.dn42.us/burble/lgregmapper) to interface with [dn42regsrv](https://git.dn42.us/burble/dn42regsrv). [collector.burble.com](https://collector.burble.com) (public internet link) The collector summarises routes from each of the burble.dn42 regions, providing a global view of network connectivity. Generally the collector will be quicker and easier to query when looking for global connectivity to an AS or network, however some functions are not supported (e.g. bgpmap functionality). Both looking glass are hosted behind [CloudFlare](https://www.cloudflare.com). ## DNS |Authoritative Service|| |:--|:--| | ns1.burble.dn42
b.delegation-servers.dn42| 172.20.129.1
fd42:4242:2601:ac53::1 | |Recursive Service|| |:--|:--| | dns.burble.dn42
b.recursive-servers.dn42| 172.20.129.2
fd42:4242:2601:ac53::53 |
burble.dn42 provides a local, anycast, authoritative and recursive DNS service. The [DNS Service](/home/dns) has it's own page. ## Registry API Service and Explorer [dn42regsrv](https://git.dn42.us/burble/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: * [https://explorer.burble.com/](https://explorer.burble.com/) (public internet link) * [http://explorer.collector.dn42/](http://explorer.collector.dn42/) (DN42 link) ## Global Route Collector * [https://grc.burble.com/](https://grc.burble.com/) (public internet link) * [https://lg-grc.burble.com/](https://lg-grc.burble.com/) (public internet link) * [http://collector.dn42/](http://collector.dn42/) (DN42 link) * [http://lg.collector.dn42/](http://lg.collector.dn42/) (DN42 link) * ssh shell@collector.dn42 The [global route collector](https://git.dn42.us/burble/grc) 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](https://git.dn42.us/burble/dn42regsrv) and published to the [dn42.burble.com](https://dn42.burble.com/) website for general use. The JSON output file can be used with [gortr](https://github.com/cloudflare/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](https://dn42.net/howto/Bird) / [Bird2](https://dn42.net/howto/Bird2)). |URL| IPv4/IPv6 |Description| |---|---|---| |[https://dn42.burble.com/roa/dn42_roa_46.json](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](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](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](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](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](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](https://dn42.burble.com/roa/dn42_roa_bird2_6.conf)   |  IPv6 Only  |   DN42 ROA data for use with Bird2 | ## Public Git Repository [git.burble.dn42](http://git.burble.dn42/) (dn42 link) [git.burble.com](https://git.burble.com/) (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 [dn42@burble.com](mailto:dn42@burble.com) for further details. ## Network Status and Reporting [dn42.status.burble.com](https://dn42.status.burble.com/) Each node in the network is monitored by [UptimeRobot](https://uptimerobot.com/) with alerts if a node becomes unavailable. Internally, nodes are measured by [netdata](https://github.com/netdata/netdata) which provides a real time view of each node. [prometheus](https://prometheus.io/) is then used to collect and store that data for historical reporting. [grafana](https://grafana.com/) is used for visualisation, but this is not currently a public service. Syslogs are exported in real time to a central logging node on the internal network.