dnsense.pub ! posts

joining dn42


I’m now on DN42, as AS4242423117. It’s a pretty neat way to explore internet-scale routing without the costs and risks of actually joining the full internet as an autonomous system.

Services

I run a authoritative DNS server, serving both the dnsense.dn42. zone and the dn42. root zone at fd00:420:69::221, and a recursive resolver at fd00:420:69::1 and 172.20.222.221 and 172.20.222.222, but IPv4 is basically obsolete on DN42​ .

There’s also the https://dnsense.dn42/ website, which doesn’t have anything yet (but might link to this page eventually).

The essential looking glass is at https://lg.dnsense.dn42/ and https://lg.dnsense.pub/​ .

Peering

A lot of the fun in DN42 is expanding your peerings, for a more robust and well-performing network.

I run a single node in the San Francisco, California region – if you want to setup a peering, contact me through my email on the registry, and include the following:

I prefer to keep my peerings on multiprotocol-BGP (where routes are sent over a single IPv6 BGP session), and extended next hop (where IPv4 traffic is routed through the IPv6 address), but I can set up IPv4 sessions and routes if your hardware doesn’t support it.

Please let me know if your node is missing IPv6 internet connectivity, as my usual endpoint is IPv6-only.