Bandura Communications offers DNS servers for some non-ICANN domains.
Addresses
The Bandura Communications DNS server can be reached at the following addresses. The load is distributed among three nodes via Anycast.
The following servers are authoritative:
| DNS |
Address |
Network |
ns1.bandura.dn42 |
172.22.149.242, fd04:234e:fc31::42 |
dn42 |
ns1.bandura.neo |
10.127.149.242, fd10:127:fc31::42 |
NeoNetwork |
ns1.bandura.crxn |
fd92:58b6:2b2::53 |
CRXN |
ns1.crxn. |
fd92:58b6:2b2::54 |
CRXN |
root-dns.neo. |
10.127.255.53, fd10:127:ffff:53:: |
NeoNetwork |
The following servers are recursive:
| DNS |
Address |
Network |
recur1.bandura.dn42 |
172.22.149.243, fd04:234e:fc31::5353 |
dn42 |
recur1.bandura.neo |
10.127.149.243, fd10:127:fc31::5353 |
NeoNetwork |
recur1.bandura.crxn |
fd92:58b6:2b2::5353 |
CRXN |
dns.neo. |
10.127.255.54, fd10:127:53:53:: |
NeoNetwork |
Recursive
Here the method specifies how the root zone is fetched. The domains are then resolved recursively.
| Zone |
Server |
Description |
Method |
dn42. |
recur1 pool |
dn42 zone |
Stub transfer |
20.172.in-addr.arpa. |
recur1 pool |
dn42 IPv4 rDNS zone |
Stub transfer |
21.172.in-addr.arpa. |
recur1 pool |
dn42 IPv4 rDNS zone |
Stub transfer |
22.172.in-addr.arpa. |
recur1 pool |
dn42 IPv4 rDNS zone |
Stub transfer |
23.172.in-addr.arpa. |
recur1 pool |
dn42 IPv4 rDNS zone |
Stub transfer |
10.in-addr.arpa. |
recur1 pool |
dn42 IPv4 rDNS zone |
Stub transfer |
d.f.ip6.arpa. |
recur1 pool |
dn42 / CRXN IPv6 rDNS zone |
Stub transfer |
hack. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
31.172.in-addr.arpa. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
100.10.in-addr.arpa. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
101.10.in-addr.arpa. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
102.10.in-addr.arpa. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
103.10.in-addr.arpa. |
recur1 pool |
ChaosVPN zone |
TSIG secured AXFR transfer from primary master server |
neo. |
recur1 pool, dns.neo. |
NeoNetwork zone |
Zone data is obtained via the registry |
127.10.in-addr.arpa. |
recur1 pool, dns.neo. |
NeoNetwork zone |
Zone data is obtained via the registry |
7.2.1.0.0.1.d.f.ip6.arpa. |
recur1 pool, dns.neo. |
NeoNetwork zone |
Zone data is obtained via the registry |
Authoritative
Bandura Communications provides an authoritative server for the following zones.
| Zone |
Server |
Method |
neo. |
root-dns.neo. |
Zone data is obtained via the registry |
127.10.in-addr.arpa. |
root-dns.neo. |
Zone data is obtained via the registry |
7.2.1.0.0.1.d.f.ip6.arpa. |
root-dns.neo. |
Zone data is obtained via the registry |
crxn. |
ns1.crxn. |
Zone data is obtained via the registry |
myip.dn42. |
ns1 pool |
Agreed with the community |
81/32.0.20.172.in-addr.arpa. |
ns1 pool |
Agreed with the community |
1.8.0.0.2.4.d.0.2.4.d.0.2.4.d.f.ip6.arpa. |
ns1 pool |
Agreed with the community |
bandura.dn42. |
ns1 pool |
Internal |
224/27.149.22.172.in-addr.arpa. |
ns1 pool |
Internal |
112/28.149.22.172.in-addr.arpa. |
ns1 pool |
Internal |
1.3.c.f.e.4.3.2.4.0.d.f.ip6.arpa. |
ns1 pool |
Internal |
bandura.neo. |
ns1 pool |
Internal |
1.3.c.f.7.2.1.0.0.1.d.f.ip6.arpa. |
ns1 pool |
Internal |
149.127.10.in-addr.arpa. |
ns1 pool |
Internal |
bandura.crxn. |
ns1 pool |
Internal |
0.0.0.2.b.2.0.6.b.8.5.2.9.d.f.ip6.arpa. |
ns1 pool |
Internal |
CRXN root server
Bandura Communications operates the top level domain server for the CRXN network. The CRXN network uses the TLD crxn.. The entries are signed with DNSSEC. An ED25519 key is used for this.
Addresses
| DNS |
Address |
|
ns1.crxn. |
fd92:58b6:2b2::54 |
CRXN |
The following other CRXN root servers, which are not operated by Bandura Communications, also exist:
| DNS |
Address |
ns2.crxn. |
- |
ns3.crxn. |
- |
ns4.crxn. |
- |
ns5.crxn. |
- |
DNSSEC
The following is the CRXN DNSKEY and its DS Record:
crxn. 900 IN DNSKEY 257 3 15 SxEseFHQWamHIiyuOBVb/tEH1+N70AFKA6YBYwiEY80=
crxn. IN DS 1624 15 2 CE9AE07ABC41D7A509530DEBEFFA79D42DE7167208435D3E1881BB5448ABAEAF
Become a root server
There are several ways to become a root server. The easiest way is to make a TSIG secured zone transfer from our server and then mirror that zone. This has to be arranged manually with us.
Another way is to sign and publish the zone yourself. For this, DNSKEY keys have to be set on all root servers. This has to be agreed with us and the CRXN community.