APNIC Home
APNIC Logo

Attributes of the APNIC Whois Database IP address (inetnum) object

inetnum template

To view the inetnum template, see APNIC Whois Database object templates.

inetnum attributes

The following describe the mandatory and optional attributes in an inetnum object.

Mandatory attributes

Attributes

Description

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 organisation 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.

Details of codes are specified in ISO 3166.

admin-c

The NIC-handle of an on-site contact person or role object. There may be more than one admin-c listed.

In the web interface, the admin-c attribute contains a link to the person or role object the NIC-handle belongs to.

To report spam or network abuse, please use the email of the admin-c.

tech-c

The NIC-handle of a technical contact person or role object. There may be more than one tech-c listed.

In the web interface, the tech-c attribute contains a link to the person or role object the NIC-handle belongs to.

To report spam or network abuse, please use the email of the tech-c.

status

All inetnum objects under APNIC Whois Database must have a status attribute. The status attribute must be one of the following values:

Status

Definition

Value set by

ALLOCATED PORTABLE

Address space allocated by APNIC or NIRs to LIRs for the purpose of subsequent distribution by LIRs to their customers. These allocations remain valid if the network changes upstream provider.

APNIC/NIR ONLY

ALLOCATED NON-PORTABLE

Address space allocated by LIRs to their customers for subsequent assignment by those customers. These allocations (and assignments made from these allocations) must be returned if the network changes upstream provider.

LIR/ISP

ASSIGNED PORTABLE

Assignments made by APNIC or NIRs, for example, small multihoming assignments or IXP assignments. These assignments remain valid if the network changes upstream provider.

APNIC/NIR ONLY

ASSIGNED NON-PORTABLE

Assignments made by LIRs to their customers for specific use within the Internet infrastructure they operate. Assignments must only be made for specific, documented purposes and may not be sub-assigned. These assignment must be returned if the network changes upstream provider.

LIR/ISP

mnt-by

The identifier of a registered mntner object used for authorisation and authentication.

In the web interface, the mntner attribute contains a link to the specified mntner.

changed

The email address of who last updated the database object and the date it occurred.

The changed attribute is not a network contact address, as it merely records who made the most recent change to the registration information. All APNIC addresses will initially record an APNIC address in this attribute, as APNIC creates the first database object.

Do not send spam or hacking complaints to this address.

source

The name of the database from which the data was obtained.

Optional attributes

Attributes

Description

rev-srv

Domain name server for the range of IP addresses specified in the inetnum.

Note: this attribute is deprecated. APNIC suggests the creation of a reverse delegation domain object to hold this information.

remarks

General remarks. May include a URL or instructions on where to send abuse complaints.

notify

The e-mail address to which notifications of changes to an object should be sent.

When this attribute contains dbmon@apnic.net, it means APNIC staff are notified of changes to the object.

Do not send spam or hacking complaints to this address.

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 controls the creation of route objects associated with the address range specified by the inetnum object.

See also:

Top  |  Database