ARIN's Routing Registry
The ARIN routing registry provides a registration service for network operators to submit, maintain, and retrieve router configuration information abstracted from the languages and syntaxes utilized by the various router configuration software. Answers to frequently asked questions (FAQs) are also provided to further clarify the use of ARIN's routing registry.
The regional routing registry serves as a repository for routing policy system information and improves ARIN's customers' ability to configure and manage their networks. It provides users with information from ARIN's IP numbers database, which contains modules for selecting, inserting, verifying, and deleting data. The routing registry system is designed to simplify, automate, and ease routing registry interaction and provides for authentication and authorization of IP registration data.
The routing registry uses the Routing Policy Specification Language (RPSL) to store object-oriented data that contain pieces of policy and administrative information in attribute-value pairs. RPSL allows a network operator to specify routing policies at various levels in the Internet routing system such as those policies affecting Autonomous System (AS) articulation and router configuration.
RPSL is not designed to be a router configuration language. Rather, it is designed so that router configurations can be generated from the description of the policy for one AS combined with the description of a router.
Querying the Routing Registry database
To query the Routing Registry database, use the following WHOIS command:
whois -h rr.arin.net <object>
For a list of instructions on querying, use the following command:
whois -h rr.arin.net help
For documentation on the routing registration service, including instructions regarding registering objects, visit one of the links on the left.
Templates for Creating Routing Registry Objects
Follow the links on the left for instructions on how to create templates for each of the Routing Registry objects.
Mirroring Requests
ARIN's routing registry server mirrors other RPSL databases. In order to be mirrored, a site must show that its routing registry data:
- is actively maintained
- has been updated within the past 30 days
- is publicly available
- expresses routing policies of use or interest to ARIN's region
Additionally, a representative of the organization submitting the mirroring request must read and agree to the terms and conditions of the "Routing Registry" section of the ARIN Number Resource Policy Manual (NPRM).
ARIN may cease mirroring if a database fails to meet the criteria listed above. Final judgement on all mirroring requests will be made by ARIN.
To request that ARIN mirror your site's RPSL database, please send an e-mail to rtreg@arin.net with "MIRRORING REQUEST" in the subject line.