Previous | Contents | Index |
Before your BIND servers can resolve inquiries originating from outside your organization, you need to register:
Before your parent domain delegates your subdomain to you, it will require that you register your network and its in-addr.arpa subdomain.
To check that your network is registered, use one of the following whois services.
ARIN | http://www.arin.net/whois/arinwhois.html |
APNIC | http://www.apnic.net/reg.html |
RIPE | http://www.ripe.net/db/whois.html |
You'll need to register before setting up your in-addr.arpa zones. There currently are three Internet Number registries:
ARIN | For the North and South America, the Caribbean, and Sub-Saharan Africa geographical areas |
APNIC | For Asia and Pacific geographical area |
RIPE | For the European geographical area |
The American Registry for Internet Numbers is a nonprofit organization that administers and registers Internet Protocol (IP) numbers to the following geographical areas:
See http://www.arin.net/RSA.html to review the American Registry for Internet Numbers, Ltd. Registration Services Agreement.
For questions, contact the ARIN Help Desk. The ARIN Help Desk is open from 8 a.m. to 7 p.m., Eastern Time. You can reach ARIN IP Registration Services in one of the following ways:
hostmaster@arin.net | |
Phone | (703) 227-0660 |
FAX | (703) 227-0676 |
ARIN templates are located at http://www.arin.net/templates.html.
Use the templates listed in Table A-1 to register your IN-ADDR.ARPA domain, networks, and autonomous systems.
If Registering This: | Use This Template: |
---|---|
Network | http://www.arin.net/templates/networktemplate.txt |
Autonomous system | http://www.arin.net/templates/asntemplate.txt |
Reverse-mapping | http://www.arin.net/templates/inaddrtemplate.txt |
ISP Network | http://rs.arin.net/templates/isptemplate.txt |
APNIC is the nonprofit Internet Registry organization for the Asia Pacific region. Networks that will be connected and located within the geographic region maintained by the Asia Pacific Network Information Center ( http://www.apnic.net/ ) should use the APNIC template located at:
ftp://ftp.apnic.net/apnic/docs/isp-address-request |
Follow the instructions that APNIC provides for submission of that template. To contact the APNIC:
Location |
APNIC
Office: Level 1, 33 Park Road Milton Queensland 4064 Australia |
Postal |
APNIC
Box 2131 Milton Queensland 4064 Australia |
info@apnic.net | |
Phone | +61-7-3367-0490 |
FAX | +61-7-3367-0482 |
Web | http://www.apnic.net |
Office hours |
9:00am - 6:00pm
Mon to Fri (Australian EST, UTC+10:00) |
Networks that will be connected and located within the European geographic regions maintained by RIPE ( http://www.ripe.net/ ) should use the European template located at:
ftp://ftp.ripe.net/ripe/forms/netnum-appl.txt |
Follow the instructions that RIPE provides for submission of that template.
To contact RIPE:
Address |
RIPE NCC
Singel 258 1016 AB Amsterdam The Netherlands |
Phone | +31 20 535 4444 |
FAX | +31 20 535 4445 |
You need to notify your parent top-level-domain of the servers that are authoritative for your domain name. Depending on the domain of which you are a member, different registration methods may apply.
For members of the generic top-level domains like com and edu, you need to contact the InterNIC.
You can access the InterNIC's web site at http://rs.internic.net for up-to-date information or send mail to:
Address |
Network Solutions Inc.
ATTN: InterNIC Registration Services 505 Huntmar Park Drive Herndon, VA 22072 |
The Internet Architecture Board (IAB) of the Internet Society (ISOC) produces numerous protocol standards and operational procedures known as Requests for Comments (RFCS). RFCs are reviewed by appropriate IAB task forces and those RFCs that are destined to become Internet standards progress through a standards track: Proposed Standard, Draft Standard, and Internet Standard.
You may obtain RFCs by e-mail or FTP from many RFC repositories around the world. To obtain information on how to retrieve RFCs, send an e-mail message to: RFC-SERVER@ISI.EDU with the following information:
TO: RFC-SERVER@ISI.EDU SUBJECT: getting rfcs. MESSAGE BODY: help: ways_to_get_rfcs |
Also, you can visit the following web site:
http://www.rfc-editor.org/ |
Table B-1 lists the RFCs associated with the DIGITAL TCP/IP Services for OpenVMS implementation.
This list is provided for convenience only and does not necessarily imply full support for each RFC. |
Protocol | Number | Title |
---|---|---|
ARP | RFC 826 | Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48-bit Ethernet Addresses for Transmission on Ethernet Hardware |
IP-E | RFC 894 | Standard for the Transmission of IP Datagrams over Ethernet Networks |
IP-IEEE | RRC 1042 | Standard for the Transmission of IP Datagrams over IEEE 802 Networks |
BOOTP | RFC 951 | Bootstrap Protocol |
RFC 1048 | BOOTP Vendor Information Extensions | |
RFC 1084 | BOOTP Vendor Information Extensions | |
CIDR | RFCS 1517, 1518, 1519, 1520 | Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy |
CSLIP | RFC 1144 | Compressing TCP/IP Headers for Low-Speed Serial Links |
DHCP | RFC 2131 | Dynamic Host Configuration Protocol |
RFC 1534 | Interoperation Between DHCP and BOOTP | |
DNS, BIND | RFC 819 | Domain Naming Convention for Internet User Applications |
RFC 920 | Domain Requirements | |
RFC 974 | Mail Routing and the Domain System | |
RFC 1032 | Domain Administrator's Guide | |
RFC 1033 | Domain Administrator's Operations Guide | |
RFC 1034 | Domain Names --- Concepts and Facilities | |
RFC 1035 | Domain Names --- Implementation and Specification | |
RFC 1101 | DNS Encoding of Network Names and Other Types | |
RFC 1183 | New DNS RR Definitions | |
RFC 1400 | Transition and Modernization of the Internet Registration Service | |
RFC 1535 | A Security Problem and Proposed Correction with Widely Deployed DNS Software | |
RFC 1536 | Common DNS Implementation Errors and Suggested Fixes | |
RFC 1537 | Common DNS Data File Configuration Errors | |
RFC 1591 | Domain Name System Structure and Delegation | |
RFC 1597 | Address Allocation for Private Internets | |
RFC 1637 | DNS NSAP Resource Records | |
Subnetting | RFC 950 | Internet Standard Subnetting Procedure |
EGP | RFC 904 | Exterior Gateway Protocol Formal Specification |
RFC 911 | RFC EGP Gateway Under Berkeley UNIX 4.2 | |
RFC 1009 | Requirements for Internet Gateways | |
RFC 1092 | EGP and Policy Based Routing in the New NSFNET Backbone | |
BGP | RFC 1771 | A Border Gateway Protocol 4 (BGP-4) |
RFC 1267 | A Border Gateway Protocol 3 (BGP-3) | |
FDDI | RFC 1390 | Transmission of IP and ARP over FDDI Networks |
FTP | RFC 959 | File Transfer Protocol |
ICMP | RFC 792 | Internet Control Message Protocol |
RFC 1256 | ICMP Router Discovery Messages | |
IP | RFC 791 | Internet Protocol |
LPD | RFC 1179 | Line Printer Daemon Protocol |
NETBIOS | RFC 1001 | Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods |
NTP | RFC 1305 | Network Time Protocol (Version 3) Specification and Implementation |
NFS | RFC 1094 | NFS: Network File System Protocol Specification |
OSPF | RFC 1583 | OSPF Version 2 |
POP | RFC 822 | Standard for the Format of ARPA Internet Text Messages |
RFC 1082 | Post Office Protocol Version 3: Extended Service Offerings | |
RFC 1321 | The MD5 Message-Digest Algorithm | |
RFC 1725 | Post Office Protocol (Version 3) | |
PPP | RFC 1332 | The PPP Internet Protocol Control Protocol (IPCP) |
RFC 1661 | The Point-to-Point Protocol (PPP) (obsoletes RFC 1548) | |
RARP | RFC 903 | Reverse Address Resolution Protocol |
RIP | RFC 1058 | Routing Information Protocol, Version 1 |
RFC 1388 | Routing Information Protocol, Version 2 | |
RLP | RFC 887 | Resource Location Protocol |
Routing | RFC 1112 | Host Extensions for IP Multicasting |
RFC 1256 | ICMP Router Discovery Messages | |
RPC | RFC 1057 | RPC: Remote Procedure Call Protocol Specification Version 2 |
SLIP | RFC 1055 | Nonstandard for Transmission of IP Datagrams Over Serial Lines: SLIP |
SMTP | RFC 821 | Simple Mail Transfer Protocol |
RFC 822 | Standard for the Format of ARPA Internet Text Messages | |
SNMP | RFC 1155 | Structure and Identification of Management Information for TCP/IP-Based Internets |
RFC 1156 | Management Information Base for Network Management of TCP/IP-Based Internets | |
RFC 1157 | A Simple Network Management Protocol | |
RFC 1158 | Management Information Base for Network Management of TCP/IP-Based Internets: MIB-II | |
RFC 1212 | Concise MIB Definitions | |
RFC 1213 | Management Information Base for Network Management of TCP/IP-Based Internets: MIB-II | |
RFC 1214 | OSI Internet Management: Management Information Base | |
RFC 1215 | Convention for Defining Traps for Use with the SNMP | |
RFC 1514 | Host Resources MIB | |
RFC 1592 | Simple Network Management Protocol Distributed Protocol Interface | |
RFC 1902 | Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1903 | Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1904 | Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1905 | Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1906 | Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1907 | Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) | |
RFC 1908 | Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework | |
Path MTU | RFC 1191 | Path MTU Discovery |
Sun ONC RPC, XDR | RFC 1790 | An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols |
TELNET | RFC 854 | Telnet Protocol Specification |
RFC 855 | Telnet Option Specification | |
RFC 856 | Telnet Binary Transmission | |
RFC 857 | Telnet Echo Option | |
RFC 858 | Telnet Suppress Go Ahead Option | |
RFC 859 | Telnet Status Option | |
RFC 860 | Telnet Timing Mark Option | |
RFC 861 | Telnet Extended Options: List Option | |
TFTP | RFC 1350 | The TFTP Protocol |
TP | RFC 868 | Time Protocol |
TCP | RFC 793 | Transmission Control Protocol |
UDP | RFC 768 | User Datagram Protocol |
XDR | RFC 1014 | XDR: External Data Representation Standard |
Previous | Next | Contents | Index |