Differences

This shows you the differences between two versions of the page.

--- chaos-dns [2020-10-02 09:26] – [1.3 Secondary name servers] victor
+++ chaos-dns [2026-03-22 17:38] (current) – victor
@@ Line 1: / Line 1: @@
 ====== - Chaosnet DNS ======
-Psilocybe.Update.UU.SE (130.238.19.25, also known as DNS.Chaosnet.NET) acts as a root DNS server for the CHaosnet class.
+DNS.Chaosnet.NET (with IP addresses corresponding to the currently three Chaosnet name servers) acts as a root DNS server for the CHaosnet class.
 It currently hosts the following domains:
-  * CH-ADDR.NET, which contains Chaosnet address mappings (similar to "IN-ADDR.ARPA").
+  * CH-ADDR.NET, which contains Chaosnet address mappings (corresponding to "IN-ADDR.ARPA").
   * Chaosnet.NET with Chaosnet infrastructure stuff and "homeless" hosts
-  * Update.UU.SE for Update Computer Club, Uppsala
+  * Update.UU.SE and dfUpdate.SE for Update Computer Club, Uppsala
   * Victor.SE for Björn Victor
-  * NoCrew.ORG for Lars Brinkhoff
+  * PDP10.SE for Lars Brinkhoff
   * Swenson.ORG for Eric Swenson
   * Bogodyne.COM for Bogodyne Metatechnics LLC
-  * Cosmic.COM for Craig Lennox
+  * STUPI.COM for Peter Löthberg
-  * GEWT.NET for gewt
+  * Sanyal.ORG for Supratim Sanyal
+  * N3UC.COM for Michael Wyrick
+  * 9grid.NET for John Floren
+  * Z54.ORG for Mete Balci
-In the Chaosnet [[https://github.com/bictorv/chaosnet-bridge|bridge program]], there is support for a ''DNS'' server over Chaosnet (using a "simple" connectionless protocol and forwarding/recursion over UDP) so Chaos-only hosts can make use of it. See [[https://github.com/bictorv/chaosnet-bridge/blob/master/CONTACTS.md|cbridge documentation]] for a protocol description.
+In the Chaosnet [[https://github.com/bictorv/chaosnet-bridge|bridge program]], there is support for a ''DNS'' server over Chaosnet (using a "simple" connectionless protocol and forwarding/recursion over UDP) so Chaos-only hosts can make use of it. See [[https://github.com/bictorv/chaosnet-bridge/blob/master/doc/CONTACTS.md|cbridge documentation]] for a protocol description.
-At DNS.Chaosnet.NET, there is also a server for the ''DOMAIN'' contact name which allows DNS queries over a stream connection, lifting the response size limit of the simple protocol (488 bytes). This contact is more standard, used by Symbolics lisp machines, and (soon) by the [[https://www.bogodyne.com|Bogodyne]] lisp system.
+At DNS.Chaosnet.NET, there is also a server for the ''DOMAIN'' contact name which allows DNS queries over a stream connection, lifting the response size limit of the simple protocol (488 bytes). This contact is more standard, used by Symbolics lisp machines, and by the [[https://www.bogodyne.com|Bogodyne]] lisp system.
-These are useful e.g. for Chaosnet-only hosts such as CADR systems to make use of DNS, at some point.
+At HOSTAB.Chaosnet.NET, there is also a server for the ''HOSTAB'' contact name, which is higher-level (see [[https://chaosnet.net/amber.html#Host-Table|here]]) and used by Lisp machines such as CADR and Lambda.
+===== - How to use the DNS server =====
+TBD: configuration descriptions.
 ===== - How to run your own DNS server =====
@@ Line 40: / Line 47: @@
   zone "." CH {
        type static-stub;
-       server-addresses { 130.238.19.25; };
+       server-addresses { 158.174.114.186; };
   };
 };
 </file>
-NOTE: this is not the perfect solution, because bind9 has a bug (2020-09-15) which causes it to crash occasionally when using this configuration (again, caused by confusion between DNS classes). You might want to configure your bind9 service to restart automatically on a crash, see https://ma.ttias.be/auto-restart-crashed-service-systemd/.
+:NOTE: This causes (2021-03-30) bind9 to crash occasionally (again, caused by confusion between DNS classes). You might want to configure your bind9 service to restart automatically on a crash, see https://ma.ttias.be/auto-restart-crashed-service-systemd/.
 If you do host your own Chaosnet data, here is an example (but see below about secondary name servers):
@@ Line 58: / Line 65: @@
 </file>
-NOTE: once you add the view for CH, you have to add one for the IN zones too. Wrap them all in, e.g.,
+:NOTE: Once you add the view for CH, you have to add one for the IN zones too. Wrap them all in, e.g.,
 <file>
 view "default" IN {
@@ Line 72: / Line 79: @@
 Example (NOTE that the address is in octal, and that the class is typically redundant):
-^ name ^ class ^ type & domain ^ address ^
+^ name ^ class ^ type ^ addr domain ^ address ^
-| UP.Update.UU.SE. | CH | A | CH-ADDR.NET. | 3143 |
+| UP.dfUPDATE.SE. | CH | A | CH-ADDR.NET. | 3443 |
 The address domain contains pointer records, just like IN-ADDR.ARPA does.
@@ Line 80: / Line 87: @@
 ^ name ^ class ^ type ^ value ^
-| 3143.CH-ADDR.NET | CH | PTR | UP.Update.UU.SE. |
+| 3143.CH-ADDR.NET. | CH | PTR | UP.dfUPDATE.SE. |
 Network names also appear in CH-ADDR.NET, in the spirit of [[rfc>1101|RFC 1101]]. They are at labels corresponding to the subnet address with zero host part, e.g. 400.CH-ADDR.NET for subnet 1, 3000.CH-ADDR.NET for subnet 6, etc.
@@ Line 99: / Line 106: @@
   file "ch-addr.zone";
   notify explicit;
-  also-notify { 130.238.19.215; };
+  also-notify { 158.174.114.186; };
 };
 </file>
 :NOTE: If you have a stable server machine with a static IP address and can open port 53, maybe you want to be secondary nameserver for the Chaosnet zones? Let me know!