The object template includes information on how to complete the attribute values.
Status Instance Search Status inetnum: [mandatory] [single] [primary/lookup key] netname: [mandatory] [single] [lookup key] descr: [mandatory] [multiple] [ ] country: [mandatory] [multiple] [ ] geoloc: [optional] [single] [ ] language: [optional] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] status: [mandatory] [single] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] mnt-lower: [optional] [multiple] [inverse key] mnt-routes: [optional] [multiple] [inverse key] mnt-irt: [mandatory] [multiple] [inverse key] last-modified: [generated] [single] [ ] source: [mandatory] [single] [ ]
inetnum: 192.168.1.0 - 192.168.1.255 netname: EXAMPLENET-AP descr: Example net Pty Ltd country: AP admin-c: DE345-AP tech-c: DE345-AP status: ASSIGNED NON-PORTABLE mnt-by: MAINT-EXAMPLENET-AP mnt-irt: IRT-EXAMPLENET-AP last-modified: 2018-08-30T07:50:19Z source: APNIC
Attribute must be included in the object. Failure to do so will result in errors.
|inetnum||The range of IP address space described by the object.|
|netname||The name of a range of IP address space.|
|descr||Description of the organization allocated or assigned the address space shown in the inetnum.|
|country||Two letter ISO 3166 code of the country or economy where the admin-c is based.|
Please use UPPERCASE letters.
EXAMPLE country: WF
|admin-c||The NIC-handle of an on-site contact ‘person’ object. As more than one person often fulfills a role function, there may be more than one admin-c listed.|
|tech-c||The NIC-handle of a technical contact ‘person’ or ‘role’ object. As more than one person often fulfills a role function, there may be more than one tech-c listed.|
|status||All inetnum objects under APNIC Whois Database must have a status attribute. The status attribute must be one of the following values:|
|mnt-by||Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.|
|mnt-irt||The identifier of a registered ‘mntner’ object used to provide information about a Computer Security Incident Response Team (CSIRT).|
|last-modified||It is a time stamp that is generated by the system to reflect when the object was last modified.|
|source||The database where the object is registered.|
Attribute may be deleted from the object. To delete an optional attribute you must also remove the attribute from the object template. Failure to do so will result in errors.
|geoloc||A latitude/longitude coordinate indicating where users of this network are located. Provides a hint to content and geolocation service providers. A blank space should be used as a separator between the two coordinates.|
EXAMPLE geoloc: -27.472834 153.014264
|language||A two-letter ISO 639-1 language code indicating a language users of this network could be expected to understand. Provides a hint to content providers.|
Multiple language attributes can be provided to suggest several languages.
|remarks||General remarks. May include a URL or instructions on where to send abuse complaints.|
|notify||The email address to which notifications of changes to this object should be sent.|
|mnt-lower||Sometimes there is a hierarchy of maintainers. In these cases, mnt-lower is used as well as ‘mnt-by.’|
|mnt-routes||The identifier of a registered ‘mntner’ object used to control the creation of ‘route’ objects associated with the address range specified by the inetnum object.|
Attribute value is generated by the database.
Instances of attribute allowed
|Attribute must appear only once in the object.|
|Attribute may appear multiple times in the object. For example, you may wish to include more than one admin-c attribute.|
Attribute search status
|Primary keys distinguish an object from all other objects in the database.|
To update a primary key, you must delete the entire object and them create a new object with the updated information.
|Attribute can be queried in the database to return the object. Please note, however, that a lookup key does not uniquely identify an object.|
|Attribute can be used when performing an inverse query using the -i flag. For example, the query|
-i mntner <MNTNER-NAME>
will return all objects with the specified maintainer in the mnt-by attribute.