This directory contains software for use on FidoNet. A full explaination of this network is available in FIDOINFO.TXT. Generally, there are several programs and utilities used for an automated network interface suitable for a public BBS or private point system. They are a: Mailer: A communications package which controls the modem hardware, and is also capable of engaging the proper initialization and transfer handshakes that have been well-defined into what is known as a "mail session." There are several different types of mailer packages available. BinkelyTerm, the one provided is currently quite for it's versatilty and power. Reader: A "Fido intelligent" simple word-processor used to read/write messages for transmission to and from the network. Packer: A utility capable of processing all drafted out-going mail to archived packets suitable for mail handling. This utility also will perform the reverse process of processing received packets, suitable for viewing with the Reader. Messages in each area are numbered sequentially once unpacked. FOSSIL: An aconym for Fido-Opus-SeaDog Interface Layer. To maintain a wide compatibility with many different types of hardware, this is a type of resident driver used by all Fido compatible software for access to communication ports, screens and keyboards. There are many other utilities which can make the operation of a node or point smoother. These functions include a database utility allowing efficient reading and access of the world-wide nodelist. There are also utilities which maintain continuity in message numbering as old ones are deleted, a special "Video FOSSIL" which provides very rapid screen access by the many different packages which can be put to use at a node or point. Some of the many different utilities which can be used are available in pd2:. DO NOT ATTEMPT A CONNECTION TO A NODE WITH THIS SOFTWARE WITHOUT FIRST OBTAINING A MATRIX ADDRESS FROM A SYSOP OF A NODE. BBIG_240.ZIP BinkleyTerm v2.40. An intellegent and widely used Mailer package suitable for use with more BBS software and point systems. (This or a similar mailer is MANDATORY). OCOM_530.ZIP OpusComm v5.30. A FOSSIL driver in .EXE file format which provides modem support for IBM PC serial ports COM1: and COM2: Good where a low amount of resident memory is available. X00V120B.ZIP X00 v1.20. A FOSSIL driver in .SYS file format (executed within CONFIG.SYS) which provides further modem support for IBM PC serial ports COM3: and COM4: as well as COM1: and COM2: (One of these or a similar FOSSIL is MANDATORY). VIBM_110.ZIP A VFOSSIL v1.10. A video FOSSIL driver beneficial on even the slowest systems. (This or similar VFOSSIL is OPTIONAL). XLAX_232.ZIP A nodelist processor which transforms the distributed nodelist (which is in text form) to a standardized data structure usable by a Mailer. This list comprises the physical structure used by the mailer for the handling of packets in a full BBS system. It is not necessary for a point system, but can be used as a reference. (OPTIONAL for points, this or a similiar package is MANDATORY for a full operating BBS). QM_100P.ZIP QMail v1.00 (patched version). A message packer. (This or similar packer is MANDATORY). READIT_6.ZIP A compiled (processed) nodelist reader and editor. (OPTIONAL). FIDO.TXT A text file of a very basic explanation of FidoNet. POINT.TXT A text file of instructions for simple set-up of a point system. AREAFIX.TXT A text file user's guide to a utility called "AreaFix." EchoMail is an popular aspect of FidoNet. To help make Sysops (node operators) and other net administrator's life alot easier, an automatic means of turning on and off Echo feeds has recently been established. It is gaining in popularity, and it is quite likely that your local node will make this service available to you. This file contains instructions for it's use. SOFTWARE.TXT This file. Finally, there is documentation for each utility providing full explanation for their use. rver and resolver software, and database files. He keeps the name server running. More than likely, this person would be the technical contact running the primary nameserver. ************************************************************************** PLEASE READ: There are several types of registrations: (a) Delegation (i.e., a portion of the US Domain name space is given to an organization running nameservers to support that branch; For example, K12.TX.US, for all K12 schools in Texas). For (a) answer questions 8 and 9. (b) Direct Registration of an IP Host. For (b) answer question 10. (c) Direct Registration of a non-IP Host. For (c) answer question 11 and 12. ************************************************************************** QUESTIONS FOR DELEGATIONS (8) PRIMARY SERVER Information. It is required to supply both the Contact information as well as hardware/software information of the primary nameserver. (9)* SECONDARY SERVER Information. It is required to supply the hardware and software information of all secondary nameservers. Domains must provide at least two independent servers that provide the domain service for translating names to addresses for hosts in this domain. If you are applying for a domain and a network number assignment simultaneously and a host on your proposed network will be used as a server for the domain, you must wait until you receive your network number assigment and have given the server(s) a net-address before sending in the domain application. Establishing the servers in physically separate locations and on different PSNs and/or networks is strongly recommended. NOTE: For those applicants not able to run nameservers, or for non-IP hosts the Name Server information is not applicable. (See #10 and #11). ========================================================================= QUESTION FOR DIRECT IP HOSTS (If you answered 8&9 do not answer 10,11,12). ========================================================================= (10) WHAT DOMAIN NAME SYSTEM (DNS) RESOURCE RECORDS (RR) AND VALUES ARE TO BE ENTERED FOR YOUR IP HOST (MUST HAVE AN A RECORD). ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Example: RRs for an INTERNET hosts. (a) DOMAIN NAME (required)...: Networthy.Santa-Clara.CA.US. (b) IP ADDRESS (required)....: A 128.9.3.123 (c) HARDWARE (opt)...........: SUN-3/11O (d) OPERATING SYS (opt)......: UNIX (e) WKS (opt)................: 128.9.3.123. UDP (tftp) TCP (ftp) (f) MX (opt).................: 10 RELAY.ISI.EDU. It is your responsibility to see that an IN-ADDR pointer record is entered in the DNS database. (For internet hosts only). Contact the administrator of the IP network your host is on to have this done. The US Domain administration does not administer the network and cannot make these entries in the DNS database. ==================================================================== QUESTIONS FOR NON-IP HOSTS (such as UUCP). ==================================================================== Many applicants have hosts in the UUCP world. Some are one hop away, some two and three hops away from their "Internet Forwarder", this is acceptable. What is important is getting an Internet host to be your forwarder. If you do not already have an Internet forwarder, there are several businesses that provide this service for a fee, (see RFC 1359 - Connecting to the Internet What Connecting Institutions Should Anticipate, ACM SIGUCCS, August 1992). Sometimes local colleges in your area are already on the Internet and may be willing to act as an Internet Forwarder. You would need to work this out with the systems administrator. We cannot make these arrangements for you. (11) INTERNET FORWARDING HOST INFORMATION (11a) What is the name of your Internet forwarding host? For example: The host Yacht-Club.MDR.CA.US uses UUCP to connect to RELAY.ISI.EDU which is an Internet host. (i.e., RELAY.ISI.EDU is the forwarding host). (11b) What is the name of your contact person at fowarding host? The Administrator of RELAY.ISI.EDU must agree to be the forwarding host for Yacht-Club.MDR.CA.US, and the forwarding host must know a delivery method and route to Networthy. No double MXing. (11c) What is the mailbox of your contact? What is the mailbox of the administrator of the forwarding host. Example: Contact Name......: John Smith Contact Email.....: js@RELAY.ISI.EDU (12) WHAT DOMAIN NAME SYSTEM (DNS) RESOURCE RECORDS (RR) AND VALUES ARE TO BE ENTERED FOR YOUR NON-IP HOST. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Example: RRs for a NON-IP host (uucp). (a) DOMAIN NAME (required).....: Yacht-Club.MDR.CA.US. (b) HARDWARE (opt).............: SUN-3/11O (c) OPERATING SYS (opt)........: UNIX (d) MX (required)..............: 10 RELAY.ISI.EDU. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PLEASE ALLOW AT LEAST 8 WORKING DAYS FOR PROCESSING THIS APPLICATION +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ US DOMAIN TEMPLATE [1/93] DO NOT USE FOR: COM, EDU, NET, ORG GOV* To register a US Domain name, please submit the following template to "US-DOMAIN@ISI.EDU". If you are registering in one of the delegated domains, please register directly with them. The instructions for obtatining the list of delegated subdomains and contacts follows: DIRECT REGISTRATIONS: Email: US-Domain@ISI.EDU Fax: 310-823-6714 Phone: 310-822-1511 US MAIL: US Domain Registrar USC/Information Sciences Institute 4676 Admiralty Way, Marina del Rey, CA 90292 DELEGATED DOMAIN REGISTRATIONS: URL: ftp://ftp.isi.edu/in-notes/us-domain-delegated.txt FTP: FTP.ISI.EDU via anonymous ftp, in-notes/us-domain-delegated.txt E-MAIL: Send message To: RFC-INFO@ISI.EDU (include as only text in the message "Help: us_domain_delegated_domains"). COM, EDU, NET, ORG, GOV REGISTRATIONS: Email: Send requests to "Hostmaster@internic.Net" __________________ * NOTE: All K12 schools, community colleges/technical schools, state and local governmentt agencies are required to register under the US domain. Only four year universities are allowed to register under EDU and only federal agencies are allowed under GOV. (See RFC 1480, "The US Domain" and RFC 1591, "The Domain Name System Structure and Delegation" for details. ========================================================================== -2- Sections or fields of this form marked with an asterisk (*) may be duplicated. (For example, if you had two phone numbers for the Administrative Contact, you would use the same number "6h" twice. PLEASE DO NOT ALTER THIS APPLICATION IN ANY WAY. ************************************************************************** 1. REGISTRATION TYPE (N)ew (M)odify (D)elete..: 2.* FULLY-QUALIFIED DOMAIN NAME: 3. ORGANIZATION INFORMATION 3a. Organization Name.....: 3b. Address Line 1........: 3b. Address Line 2........: 3c. City..................: 3d. State.................: 3e. Zip/Code..............: 4. DESCRIPTION OF ORG/DOMAIN: 5. Date Operational......: 6. ADMINISTRATIVE CONTACT OF ORG/DOMAIN 6a. NIChandle (if known)..: 6b. Whole Name............: 6c. Organization Name.....: 6d. Address Line 1........: 6d. Address Line 2........: 6e. City..................: 6f. State.................: 6g. Zip/Code..............: 6h.* Voice Phone...........: 6i.* Electronic Mailbox....: 7. TECHNICAL AND ZONE CONTACT 7a. NIChandle (if known)..: 7b. Whole Name............: 7c. Organization Name.....: 7d. Address Line 1........: 7d. Address Line 2........: 7e. City..................: 7f. State.................: 7g. Zip/Code..............: 7h.* Voice Phone...........: 7i.* Electronic Mailbox....: - 3 - FILL OUT QUESTION 8 AND 9 FOR DELEGATIONS ONLY (i.e those organizations running nameservers for a branch of the US Domain namespace, for example: k12..us). 8. PRIMARY SERVER: HOSTNAME, NETADDRESS 8a. NIChandle (if known)..: 8b. Whole Name............: 8c. Organization Name.....: 8d. Address Line 1........: 8d. Address Line 2........: 8e. City..................: 8f. State.................: 8g. Zip/Code..............: 8h.* Voice Phone...........: 8i.* Electronic Mailbox....: 8j. Hostname..............: 8k.* IP Address ...........: 8l.* HARDWARE..............: 8m.* OPERATING SYS.........: 9. * SECONDARY SERVER: HOSTNAME, NETADDRESS 9a.* Hostname..............: 9b.* IP Address............: 9c.* HARDWARE..............: 9d.* OPERATING SYS.........: FILL OUT QUESTION 10 FOR DIRECT REGISTRATIONS IP HOSTS (if you answered 8 & 9, do not answer 10, 11, and 12) 10. RESOURCE RECORDS (RRs) FOR IP INTERNET HOSTS 10a. DOMAIN NAME ..........: 10b.* IP ADDRESS (required).: 10c. HARDWARE .............: 10d. OPERATING SYS ........: 10e. WKS ..................: 10f.* MX ...................: It is your responsibility to see that an IN-ADDR pointer record is entered in the DNS database. Contact the administrator of the IP network your host is on to have this done. FILL OUT QUESTIONS 11 AND 12 FOR NON-IP HOSTS (such as UUCP) 11. FORWARDING HOST INFORMATION 11a. Forwarding Host.......: 11b. Contact Name (req)....: 11c. Contact Email (req)...: 12. RESOURCE RECORDS (RRs) FOR NON-IP HOSTS (UUCP) 12a. DOMAIN NAME ..........: 12b. HARDWARE .............: 12c. OPERATING SYS ........: 12d.* MX (required).........: ************************************************************************** DISCLAIMER By the registration of your name on the Internet, the IANA, the InterNIC, Network Solutions Inc., the University of Southern California, and the National Science Foundation are accepting in good faith that you have the right to the use the name. The IANA and InterNIC/Network Solutions' function in registering names on the Internet is to assure that the name does not conflict with any other name in the name space requested. The user by its registration and use of the name and/or their continued use of an existing name, agrees, as part of their request for name registration, to indemnify and hold harmless from any and all costs, fees, expenses arising from litigation involving trademark, trade name, service mark, and any other name infringements, or other reasons, the IANA, the InterNIC, Network Solutions Inc., the University of Southern California, and the National Science Foundation. The party requesting registration of this name certifies that to her/his knowledge, the use of this name does not violate trademark or other statutes. Registering a domain name does not confer any legal rights to that name and any disputes between parties over the rights to use a particular name are to be settled between the contending parties using normal legal methods (See RFC 1591). **************************************************************************