RIPE Database docs
Sidebar Navigation

Introduction to the RIPE Database

RIPE Database Documentation Overview

Intended Audience

Conventions Used in the RIPE Database Documentation

What is the RIPE Database

Purpose and Content of the RIPE Database

History of the RIPE Database

Personal Data Database Management and Reponsabilities

RIPE Database Structure

Database Object

Primary and Secondary Objects

List of Primary Objects

List of Secondary Objects

The Attributes in Database Objects

Attribute Names

Attributes in an Object

Attribute Values

Attribute Properties

How to Organise Your Data

REST API Data model

RPSL Object Types

Descriptions of Primary Objects

Descriptions of Secondary Objects

Available Databases

RIPE Database

TEST Database

Release Candidate Database

Experimental Databases

Update Methods

RESTful API

Webupdates

Syncupdates

Email Updates

Updating Objects in the RIPE Database

Format of the Update Message

Accessing the Object Templates

Object Processing

Update Operations

Historical Data

Special Considerations for Object Creation

Garbage Collection

Dry run

Set Objects

Notifications

Acknowledgment Message

Notification Messages

Authorisation

Authorisation Model

Using the Authorisation Methods

Security of Data Using Authorisation

Protection of PERSON and ROLE Objects

Protection of AUT NUM Object Space

Protection of Address Space

Protection of Route Object Space

Protection of Reverse Delegation Objects

Protection of Objects with Hierarchical Names

Protecting Membership of a Set

Referencing an ORGANIZATION Object

Referencing an IRT Object

IRT Object

Force Delete Functionality

Request ENUM delegation

Request DNSSEC delegation

How to Query the RIPE Database

The Structure of a Query

Web Query Form

RESTful API Queries

Command Line Queries

Query Responses

Registration Data Access Protocol

Access to Personal Data

Types of Queries

Queries Using Primary and Lookup Keys

Queries for IP Networks

Queries for Autonomous Systems

More and Less Specific Lookups For Reverse Domains

Inverse Queries

Abuse Contacts

Grouping the RIPE Database Output

Filtering the Query Reponse

IRR Toolset Support

Persistent Connections and Keeping State

Getting All the Members of Set objects

Access Control for Queries

RIPE NCC Global Resource Service

Other Query Flags

Referenced Objects in Query Response

Historical Queries

Related Software and Tools

Geolocation in the RIPE Database

RIPE Database Mirror

Setup RIPE Database Mirror

Near Real Time Mirroring v3

Near Real Time Mirroring v4

Access to NRTM

Tables of Query Types Supported by the RIPE Database

How to Recover Access to a Maintainer Object

Installation and Development

Getting started on macOS

Getting started on Ubuntu Linux

Building whois

Configure MariaDB

Coding standard

Installation instructions

Database Support

Support Overview

Clean up of Unreferenced Data

Database Security

Configuring Reverse DNS

Database Business Rules

Highlighted Values in the RIPE Database

Create First Role Mntner

Removal of personal data

Release Notes

FAQ

Appendices

Appendix A Syntax of Object Attributes

Appendix B Copyright Statement

Appendix C RIPE Database Query Server Response Codes and Messages

Appendix-D--Route-Object-Creation-Flowchart

Appendix-E--Domain-Object-Creation-Flowchart

Appendix F Special Considerations for Object Types

Appendix G Object Types with Personal Data

Appendix H PGP Authentication Method

Appendix I Client Certificate Authentication

Appendix J Ripe Test Database

Appendix K API Keys

Glossary

Legal Information

RIPE Database Acceptable Use Policy

HTML Terms And Conditions

All Documentation Combined

On this page

Appendix C- RIPE Database Query Server Response Codes and Messages ​

If the server encounters a problem, an error message is returned as a query result. The format of an error message is as follows:

%ERROR:#:<message>,

where # is the error or response code and <message> is a short description of the problem. There are no white spaces in this line, except in the <message> string. This maybe followed by a more descriptive message, each line of which starts with % followed by a white space and some text.

Example:

% This is the RIPE Database query server. 
% The objects are in RPSL format. 
%
% The RIPE Database is subject to Terms and Conditions.  
% See http://www.ripe.net/db/support/db-terms-conditions.pdf 

%ERROR:101: no entries found  
%  
% No entries found in the selected source(s).

Query Errors ​

%ERROR:101: no entries found No entries were found in the selected source(s).

%ERROR:102: unknown source Unknown source was supplied as argument to the -s query flag. Use -q sources for a list of available sources.

%ERROR:103: unknown object type Unknown object type is specified as an argument to the -T query flag.

%ERROR:104: unknown attribute Unknown argument is specified to the inverse query flag (-I). See Queryingthe RIPE Database for more information.

%ERROR:105: attribute is not searchable The argument specified for the inverse query flag is not a searchable attribute. See Queryingthe RIPE Database for more information.

%ERROR:106: no query argument specified No query argument has been specified in the query.

%ERROR:107: input line too long Input exceeds the maximum line length.

%ERROR:108: bad character in input An invalid character was passed in the query. The only allowed characters are letters,numbers and -_:+=.,@/?'

%ERROR:109: invalid combination of flags passed The specified query flags cannot be included in the same query.

%ERROR:110: multiple use of flag The same flag cannot be used multiple times.

%ERROR:111: invalid option supplied Query flag that does not exist was given. Use the help query to see the valid options.

%ERROR:112: unsupported query-mM query options are not allowed on very large ranges/prefixes.

%ERROR:114: unsupported query Search key doesn't match any known query types.

%ERROR:115: invalid search key Search key entered is not valid for the specified object type(s).

%ERROR:116: unsupported query Versions are not supported for PERSON/ROLE objects.

%ERROR:117: version cannot exceed X for this object Versions are numbers greater or equal to 1 but cannot exceed the object's current version number.

Access Errors ​

%ERROR:201: access denied Access from the host has been temporarily or permanently denied because of excessive querying. You should contact a customer service representative to discuss this problem.

%ERROR:202: access control limit reached Limit of returned objects has been reached. The connection is terminated. Continued attempts to excessively query the database will result in permanent denial of service. See section Access Control for Queries for more information.

%ERROR:203: address passing not allowed The host is not registered as a proxy and is not allowed to pass addresses on the query line (-V flag). See section Access Control for Queries for more information.

Connection Errors ​

%ERROR:301: connection has been closed The connection is administratively or abnormally closed.

%ERROR:302: referral timeout The connection was closed due to referral timeout.

%ERROR:303: no referral host Referral host cannot be found.

%ERROR:304: referral host not responding The connection to the referral host cannot be established.

%ERROR:305: connection has been closed The connection to the server has been closed after a period of inactivity.

%ERROR:306: connections exceeded Number of connections from a single IP address has exceeded the maximum number allowed.

NRTM Errors ​

%ERROR:401: invalid range: Not within <rst>-<last> This happens when the requested range or part of it is outside the serial numbers available at the server. <rst> is the lowest serial number available. <Last> is the most recent serial number available.

Warnings ​

%WARNING:901: duplicate IP flags passed More than one IP flag (-x, -M, -m, -L, -l, -c, or -b) was passed to the server. Only the last one in the list of query flags will be used for this query.

%WARNING:902: useless IP flag passed An IP flag (-x, -M, -m, -L, -l, -c, or -b) was passed to the server when query did not include an IP key as the argument.

Last updated:

Pager
Previous pageAppendix B Copyright Statement
Next pageAppendix D Route Object Creation Flowchart