Whois object types
Records in the APNIC Whois Database are called 'objects'. Examples of different objects include people, IP address allocations, AS numbers, and domains (for reverse delegations). Objects can make reference to other objects. For example, the IP address allocation object called inetnum makes reference to a person and maintainer.
Objects are lists of "attribute-value" pairs in plain text.
Objects consist of standard attribute tags and values. Attribute tags must never be changed as this will result in errors when those changes are submitted to the database. Values for particular attributes are specified in templates. The appropriate value should be specified in each template to reduce the chance of errors.
Overview of Objects
At this time, there are seventeen types of objects in the APIC Whois Database. Each includes a range of mandatory and optional attributes. Some attributes may be present multiple times.
- Mandatory attributes must be included in the object.
Failure to do so will result in errors. Attempts to update objects that do not include mandatory attributes will be rejected. - Optional attributes may be omitted from the object.
Where an optional attribute is omitted, the attribute tag must also be omitted from the object template. Failure to do so will result in errors and the update will be rejected. - Multiple attributes can be supplied where permitted, in which case the order of the multiple instances is not guaranteed to be preserved.
In some cases, an alternative method to specify a longer value with 'line folding' (i.e., across multiple lines of record) can be used, and this does preserve the text order. - The name of each object is always a mandatory attribute, and must always be the first attribute of an object.
| Object name | Description |
|---|---|
| as-block | Shows the range of AS numbers delegated to Regional and National Internet Registries. Used to stop unauthorized creation of aut-num objects |
| as-set | A group of Autonomous systems with the same routing policies |
| aut-num | Contains details of the registered holder of an Autonomous System number and their routing policy for that AS |
| domain | Contains details of in-addr.arpa (IPv4) and ip6.arpa (IPv6) reverse DNS delegations |
| filter-set | Defines the policy filter to be applied to a set of routes |
| inet6num | Contains details of an allocation or assignment of IPv4 address space |
| inetnum | Contains details of an allocation or assignment of IPv4 address space |
| inet-rtr | Represents an Internet router within a routing registry |
| key-cert | Stores PGP (Pretty Good Privacy) certificate for user with mntner objects for authentication when performing object updates |
| mntner | Contains details of the authorized agent able to make changes to APNIC Whois Database objects. It also includes details of a process that verifies that the person making the changes is authorized to do so. All mntner objects must be forwarded to APNIC staff as they are not created automatically. |
| peering-set | Defines a set of peering listed in the object's peering attribute |
| person | Contains details of the technical or administrative contact responsible for the object where it is referenced |
| role | Contains details of technical or administrative contacts as represented by a role, performed by one or more people within an organization, such as a help desk or network operations centre |
| route | Represents a single IPv4 route injected into the Internet routing mesh |
| route6 | Represents a single IPv6 route injected into the Internet routing mesh |
| route-set | Defines a set of routes that can be represented by route objects or address prefixes |
| rtr-set | A rtr-set object defines a set of routers |