domain.txt file
This file is used by DNS server as a source for resolving URL names into IP numbers. HostFileSystemGlobal shows the default location for this file. The generalized format for this file is:
$TTL <ttl value> <domain name>. IN SOA <nameserver name>. <user.email>. ( <serial>; serial number <refresh>; refresh value <retry>; retry value <expire>; expire value <n-ttl>; negative caching TTL of 1 day <domain name>. IN NS <authoritative NS name>. <domain name>. IN NS <authoritative NS name>. ... <hostname>. IN A <IP address> <hostname>. IN A <IP address> ...
Under jnos, the SOA record is ignored, but the admin might find it useful for keeping various versions during development.
The DNS feature of JNOS functions similarly to "bind" in a unix environment. This file content is similar to the "named.zone" files of bind. Using a serch engine and reading the documentation for bind and these files give significant detail to the content and format of this file.
An excerpt from this file might look like:
hamradio.ucsd.edu. 147682 IN A 132.239.1.144 HamGate.Ottawa.ampr.org. 341188 IN A 44.102.132.1 k8rra.ampr.org. IN A 44.102.132.20 gfvhome.org. IN A 192.138.1.0 toy.gfvhome.org. IN A 192.168.1.21 tango.gfvhome.org. IN A 192.168.1.32
There is some controversy surrounding the content of this file relative to remote DNS servers. Specifically the content of "domain.txt" file seen as:
ampr.org. 345299 IN NS dns.iarc.org. ampr.org. 345299 IN NS ns1.nosc.mil.
produces a similar result to the use of domain command in AutoexecNosFile as follows:
domain addserver dns.iarc.org domain addserver ns1.nosc.mil
The debate surrounding this issue is tied to effectiveness of processing and representation for the rest of the world. Each site administrator will choose which alternative to use.
Attachment of example domain.txt files is encouraged here with an explanation as to it's unique features in the application.