This is an old revision of the document!
Christopher Stacy implemented DNS support for ITS, which I later (ca 2005) hacked to get it working in my setup. The advantage is of course that you don't need to keep SYSHST;H3TEXT updated, but instead use the standard domain name system. Drawbacks are that programs need to be recompiled, and that some aren't yet fully compatible with the RESOLV library.
So: all this is optional!!
A tape file should appear here, including the diffs.
Compile DQDEV and install it as a “driver” for the DOMAIN: device.
:midas device;jobdev domain_hack;dqdev
Optional: Update the domain search list in VICTOR;RESOLV (see below).
Recompile programs which use SYSNET;RESOLV to instead use VICTOR;RESOLV (or where you choose to put it).
(A list should appear here soon - note that COMSAT need not be recompiled!).
When you have recompiled the programs, they will use DNS automatically.
Print “database” (never really updated):
:print domain:foo;.file. (dir)
Create new “database” (do this once, don't mess with it):
:print domain:xyzzy;..new. (dat)
Dig in the DNS:
:dig in;a;ftp.its.os.org :dig ch;hinfo;up.update.uu.se
See notes in files but also note in particular:
The root server is hardcoded at ROOHST/ROOADR to J.ROOT-SERVERS.NET with address 192.58.128.30. If you set up your firewall as (strongly!) suggested above, this doesn't matter.
The “main domain list” is set after MAKD10 to ITS.OS.ORG (instead of AI.MIT.EDU), both rather useless (but doesn't matter since RESOLV has its own search list).
The Chaosnet address-to-domain translation domain is hardcoded to CH-ADDR.UPDATE.UU.SE after label RCHADR and after HSTB10. This only matters if you use chaosnet.
The domain search list hardcoded to “.update.uu.se” and “.its.os.org” at DOMS just before HSTADN. You probably want to update this.
The Chaosnet address-to-domain translation domain is hardcoded to CH-ADDR.UPDATE.UU.SE after HSTSRC (see note above).