Test Whois Database

APNIC also operates a test database where users may learn how to use the APNIC Whois Database.

Getting started

Before you can register any resources in the APNIC Test Whois Database, you must first create your own person and maintainer objects, using the three-step process described below.

Step 1

Create a person object based on the template below:

- - - - - - - - - - 8< - - - - - - - - - - - - -
person:
address:
country:
phone:
fax-no:
e-mail:
nic-hdl:
remarks:
notify:
abuse-mailbox:
mnt-by:        MAINT-AP-TESTAPNIC-NULL
changed:
source:        TESTAPNIC
- - - - - - - - - - - - - - - - - - - - - - - -

In the mnt-by attribute, you must specify:

mnt-by:  MAINT-AP-TESTAPNIC-NULL
source:  TESTAPNIC

Email the completed person object to: test-dbm@apnic.net

When you receive an email from the APNIC Test Whois Database telling you that the submission was a success, you can proceed with the creation of a maintainer object.

Step 2

Create a maintainer object based on the template below:

- - - - - - - - - - 8< - - - - - - - - - - - - -
mntner:
descr:
country:
admin-c:
tech-c:
upd-to:
mnt-nfy:
auth:
remarks:
notify:
mnt-by:
referral-by:  MAINT-AP-TESTAPNIC-NULL
changed:
source:       TESTAPNIC
- - - - - - - - - - - - - - - - - - - - - - - -

Refer to your new test database person objects ‘nic-hdl’ in the admin-c and tech-c attributes.

In the referral-by attribute, you must specify:

MAINT-AP-TESTAPNIC-NULL

Email the completed maintainer object to: test-dbm@apnic.net

Step 3

Update the maintainer of your person object (optional)

Follow normal APNIC Whois Database update email procedures to update your person object and then submit the object to:

test-dbm@apnic.net

To check your object has successfully been created, you can query the Test Whois database.

Use the following command syntax:

whois -h testwhois.apnic.net

Creating IP address objects in the APNIC Test Whois Database

To create inetnum or inet6num objects in the APNIC Test Whois Database with a status of ALLOCATED PORTABLE or ASSIGNED PORTABLE (status for resources delegated directly from APNIC), you must specify:

mnt-by:  MAINT-AP-TESTAPNIC-NULL 

If you attempt to use any other maintainer in this 
attribute, your submission will fail.

Note: You may specify any maintainer you choose when creating inetnum and inet6num objects with a status of ALLOCATED NON-PORTABLE or ASSIGNED NON-PORTABLE.

Normal APNIC Whois Database update email procedure

Once the person and mntner object have been created it is good
practice to replace MAINT-AP-TESTAPNIC-NULL with your newly created mntner object. This means your new mntner object protects your person object.

Email your updated person object template, with the new mntner placed in the mnt-by attribute, to test-dbm@apnic.net

- - - - - - - - - - 8< - - - - - - - - - - - - -
person:
address:
country:
phone:
fax-no:
e-mail:
nic-hdl:
remarks:
notify:
abuse-mailbox:
mnt-by:        MAINT-EXAMPLETEST-AP
changed:
source:        TESTAPNIC
- - - - - - - - - - - - - - - - - - - - - - - -

Note: When updating objects with the Normal APNIC Whois Database update email procedure, you would need to replace ‘MAINT-NEW’ with your new maintainer and add the ‘password:’ attribute (see below):

- - - - - - - - - - 8< - - - - - - - - - - - - -
person:
address:
country:
phone:
fax-no:
e-mail:
nic-hdl:
remarks:
notify:
abuse-mailbox:
mnt-by:        MAINT-EXAMPLE-NEW-AP
changed:
source:        APNIC
password:
- - - - - - - - - - - - - - - - - - - - - - - -