domain
Object Template
The object template includes information on how to complete the attribute values.
Status Instance Search Status domain: [mandatory] [single] [primary/lookup key] descr: [mandatory] [multiple] [ ] country: [optional] [single] [ ] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] zone-c: [mandatory] [multiple] [inverse key] nserver: [optional] [multiple] [inverse key] sub-dom: [optional] [multiple] [inverse key] dom-net: [optional] [multiple] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] mnt-lower: [optional] [multiple] [inverse key] refer: [optional] [single] [ ] last-modified: [generated] [single] [ ] source: [mandatory] [single] [ ]
Example
domain: 1.168.192.in-addr.arpa descr: reverse domain object for 192.168.1.0/24 country: AP admin-c: DE345-AP tech-c: DE345-AP zone-c: DE345-AP nserver: ns1.example.com nserver: ns2.example.com mnt-by: MAINT-EXAMPLENET-AP mnt-lower: MAINT-EXAMPLENET-AP last-modified:2018-08-30T07:50:19Z source: APNIC
Attribute status
Mandatory
Attribute must be included in the object. Failure to do so will result in errors.
Attribute | Description |
---|---|
domain | The name of the reverse delegation.
For IPv4 reverse delegation, use the format x.x.x.x.in-addr.arpa. EXAMPLE 181.137.202.in-addr.arpa 137.202.in-addr.arpa For IPv6 reverse delegations, use the format x.x.x.x.ip6.arpa. |
descr | The name of the organization responsible for the reverse delegation. Or can describe the use of the IP range described in the domain object.
EXAMPLE Reverse delegation for ExampleNet-WF Reverse delegation for 202.137.181.0/20 Reverse delegation for Sparkynet customer |
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.
|
zone-c | The NIC-handle of a ‘person’ or ‘role’ object with authority over a zone. There may be more than one zone-c listed.
In the web interface, the zone-c attribute contains a link to the ‘person’ or ‘role’ object the NIC-handle belongs to. |
nserver | A list of nameservers for a domain object. A minimum of one nameserver is mandatory. |
mnt-by | Lists a registered ‘mntner’ used to authorize and authenticate changes to this object.
|
last-modified | It is a time stamp that is generated by the system to reflect when the object was last modified.
last-modified: 2018-08-30T07:50:19Z |
source | The database where the object is registered.
|
Optional
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.
Attribute | Description |
---|---|
country | Two letter ISO 3166 code of the country or economy where the admin-c is based.
Please use UPPERCASE letters. EXAMPLE country: WF |
sub-dom | This attribute is not applicable to reverse domains. Do not use this attribute.
APNIC Whois Database uses RIPE v3 database software. Some functions and options in RIPE software are not applicable to the APNIC Whois Database. |
dom-net | This attribute is not applicable to reverse domains. Do not use this attribute.
APNIC Whois Database uses RIPE v3 database software. Some functions and options in RIPE software are not applicable to the APNIC Whois Database. |
remarks | General remarks. May include a URL or email address. |
notify | The email address to which notifications of changes to this object should be sent.
|
mnt-lower | The identifier of a registered mntner object used to authorize the creation of reverse domain objects more specific than the reverse domain specified by this object. |
refer | This attribute is not applicable to reverse domains. Do not use this attribute.
APNIC Whois Database uses RIPE v3 database software. Some functions and options in RIPE software are not applicable to the APNIC Whois Database. |
Generated
Attribute value is generated by the database.
Instances of attribute allowed
Single |
Attribute must appear only once in the object. |
Multiple |
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 key |
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. |
Lookup key |
Attribute can be queried in the database to return the object. Please note, however, that a lookup key does not uniquely identify an object. |
Inverse key |
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. |