Add pingable.burble.dn42
This commit is contained in:
parent
e696ba89c6
commit
5b44fb0b72
@ -50,6 +50,19 @@ Both looking glass are hosted behind [CloudFlare](https://www.cloudflare.com).
|
|||||||
burble.dn42 provides a local, anycast, authoritative and recursive DNS service.
|
burble.dn42 provides a local, anycast, authoritative and recursive DNS service.
|
||||||
The [DNS Service](/home/dns) has it's own page.
|
The [DNS Service](/home/dns) has it's own page.
|
||||||
|
|
||||||
|
## Pingable IP address
|
||||||
|
|
||||||
|
* pingable.burble.dn42
|
||||||
|
* 172.20.129.5
|
||||||
|
* 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
|
## Registry API Service and Explorer
|
||||||
|
|
||||||
[dn42regsrv](https://git.dn42.us/burble/dn42regsrv) is a REST API for the DN42 registry
|
[dn42regsrv](https://git.dn42.us/burble/dn42regsrv) is a REST API for the DN42 registry
|
||||||
|
@ -19,7 +19,8 @@ burble.dn42 IP addresses
|
|||||||
|dns.burble.dn42|172.20.129.2|fd42:4242:2601:ac53::53|Recursive DNS Resolver|
|
|dns.burble.dn42|172.20.129.2|fd42:4242:2601:ac53::53|Recursive DNS Resolver|
|
||||||
|www.burble.dn42|172.20.129.3|fd42:4242:2601:ac80::1|Website|
|
|www.burble.dn42|172.20.129.3|fd42:4242:2601:ac80::1|Website|
|
||||||
|collector.dn42|172.20.129.4|fd42:4242:2601:ac12::1|Global Route Collector|
|
|collector.dn42|172.20.129.4|fd42:4242:2601:ac12::1|Global Route Collector|
|
||||||
| |_172.20.129.5-31_| |_Unallocated_|
|
|pingable.burble.dn42|172.20.129.5|fd42:4242:2601:ac05::1|Pingable IP Address|
|
||||||
|
| |_172.20.129.6-31_| |_Unallocated_|
|
||||||
|collector.burble.dn42|None|fd42:4242:2601:36::b|burble.dn42 Route Collector|
|
|collector.burble.dn42|None|fd42:4242:2601:36::b|burble.dn42 Route Collector|
|
||||||
<br/>
|
<br/>
|
||||||
|
|
||||||
|
@ -10,6 +10,10 @@ A log of changes to the burble.dn42 network.
|
|||||||
|
|
||||||
## burble.dn42 Maintenance Log
|
## burble.dn42 Maintenance Log
|
||||||
|
|
||||||
|
#### 25th July 2019
|
||||||
|
|
||||||
|
Add pingable.burble.dn42
|
||||||
|
|
||||||
#### 21st July 2019
|
#### 21st July 2019
|
||||||
|
|
||||||
Decommissioning of dn42-ru-mos1 and dn42-us-sea1
|
Decommissioning of dn42-ru-mos1 and dn42-us-sea1
|
||||||
|
@ -178,6 +178,14 @@ $
|
|||||||
|
|
||||||
Once peering is established I have a BGP looking glass [here](https://lg.burble.com/) (public internet link) and global route [collector](https://collector.burble.com) which can be used to check routing.
|
Once peering is established I have a BGP looking glass [here](https://lg.burble.com/) (public internet link) and global route [collector](https://collector.burble.com) which can be used to check routing.
|
||||||
|
|
||||||
|
#### Automated reachability and latency testing
|
||||||
|
|
||||||
|
pingable.burble.dn42 (172.20.129.5 / fd42:4242:2601:ac05::1) is a dedicated address
|
||||||
|
that responds to ping and traceroute and may be used for automated reachability or
|
||||||
|
link quality testing. Please be considerate when configuring automated tests and
|
||||||
|
set a reasonable test frequency. In all cases, the frequency must not be more
|
||||||
|
than once a second.
|
||||||
|
|
||||||
---
|
---
|
||||||
#### Network Information
|
#### Network Information
|
||||||
The burble.dn42 is fully meshed between nodes using wireguard tunnels and VXLAN. However, the network is configured as a number of sub-AS regions within a single BGP confederation to allow for regional services and to reduce the number of iBGP sessions. See the [about](/about) page for more details and a network diagram.
|
The burble.dn42 is fully meshed between nodes using wireguard tunnels and VXLAN. However, the network is configured as a number of sub-AS regions within a single BGP confederation to allow for regional services and to reduce the number of iBGP sessions. See the [about](/about) page for more details and a network diagram.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user