From randy@psg.com Wed Apr 28 10:16:36 1993 Received: from rip.psg.com by fido.wps.com (5.67/1.34) id AA00587; Wed, 28 Apr 93 10:16:28 -0700 Received: by rip.psg.com (Smail3.1.28.1 #3) id m0noFk6-000303C; Wed, 28 Apr 93 10:16 PDT Message-Id: From: randy@psg.com (Randy Bush) Subject: IP Address for RGNET (fwd) To: tomj@fido.wps.com (Tom Jennings) Date: Wed, 28 Apr 1993 10:16:22 -0700 (PDT) Content-Type: text Content-Length: 969 Status: OR Forwarded message: From internic.net!netreg Wed Apr 28 10:12:41 1993 From: netreg@internic.net (Network Registration Role Account) Message-Id: <9304281547.AA12540@rs> Subject: IP Address for RGNET To: randy@psg.com Date: Wed, 28 Apr 93 11:47:50 EDT X-Mailer: ELM [version 2.3 PL2] 28-Apr-93 Dear Randy Bush: RGNET has been assigned 1 Class C net number(s). The address(es) is (are) 198.133.206.0. The NIC handle of the technical POC is RB366. It is suggested that host number zero in any network be reserved (not used), and the host address of all ones (255 in class C networks) in any network be used to indicate a broadcast datagram. The association between addresses used in the particular network hardware and the Internet addresses may be established and maintained by any method you select. Use of the address resolution procedure described in RFC-826 is encouraged. Thanks again for your cooperation! InterNIC Registration Services From randy@psg.com Wed Apr 28 14:38:18 1993 Received: from rip.psg.com by fido.wps.com (5.67/1.34) id AA01135; Wed, 28 Apr 93 14:38:08 -0700 Received: by rip.psg.com (Smail3.1.28.1 #3) id m0noJpE-000303C; Wed, 28 Apr 93 14:37 PDT Message-Id: From: randy@psg.com (Randy Bush) Subject: 206.133.198.in-addr.arpa registration To: hostmaster@internic.net Date: Wed, 28 Apr 1993 14:37:56 -0700 (PDT) Cc: sysadm@NSD.3Com.COM, lgillam@bridge2.NSD.3Com.COM, tomj@fido.wps.com (Tom Jennings) Content-Type: text Content-Length: 2641 Status: OR [netinfo/in-addr-template.txt] [ 04/93 ] The Internet uses a special domain to support gateway location and Internet address to host mapping. The intent of this domain is to provide a guaranteed method to perform host address to host name mapping, and to facilitate queries to locate all gateways on a particular network in the Internet. IN-ADDR.ARPA Registration The following information is needed for delegation of registered networks in your domain for inclusion in the IN-ADDR.ARPA zone files: * the IN-ADDR.ARPA domain * the Network name * the Hostnames of the two hosts on networks that will be acting as IN-ADDR servers IN-ADDR domains are represented using the network number in reverse. For example, network 123.45.67.0's IN-ADDR domain is represented as 67.45.123.IN-ADDR.ARPA. For example: IN-ADDR domain Network Name IN-ADDR Servers (Hostname) (NetAddress) (CPUType/OpSys) 41.192.IN-ADDR.ARPA NET-TEST-ONE BAR.FOO.EDU 123.45.67.89 VAX-II/VMS ONE.ABC.COM 98.76.54.32 SUN/UNIX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NOTE: Unless specified, new hosts registered as IN-ADDR servers will be registered in the root servers only and will not appear in the HOSTS.TXT file. Please have the Network Coordinator complete and return the following information for those networks needing IN-ADDR registration. IN-ADDR domain Network Name IN-ADDR Servers ============== ============ =============== 206.133.198.in-addr.arpa RGNET RAIN.PSG.COM 147.28.0.34 SUN / UNIX NS.3COM.COM 129.213.128.2 SUN / UNIX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Completed templates and questions can be directed to Hostmaster at HOSTMASTER@INTERNIC.NET, or mailed to: Network Solutions InterNIC Registration Service 505 Huntmar Park Drive Herndon, VA 22070