1. APNIC Open Policy Meeting
APNIC Reverse DNS Status
August 30, Taipei
Bruce Campbell

2. Use of APNIC Reverse DNS
Delegation of IP space from APNIC to ISPs etc. (in-addr.arpa / ip6.int )
Not automatically set up as part of an IP allocation from APNIC.

3. Reverse Delegations
Stored in APNIC WHOIS database as domain objects. ( in-addr.arpa)
Automatic form checks domain and nameserver configuration for sanity.
Checklist and online form at: ( updates also possible)
Assumes basic knowledge of Reverse DNS

4. Limitations of APNIC System
Classful delegations (limited to the ‘.’ boundaries). (/19 allocation must delegate 32 /24s)
Must have nameservers set up before requesting delegation.
Verification can take excessive time if nameservers are ‘far’ from Brisbane office.
Changes made public (officially) only once per business day (not on weekends).

5. Status of Delegations System in use since August 1999.
Today’s update – delegations resulting in 1104 generated zone files.
‘Hanging’ Delegations (ie, /16 zone file delegated elsewhere, but /24 delegations in database) still occur occasionally.
Processing time is ~5minutes (depends on load on master whois server)

6. Nameserver Status
Svc00.apnic.net currently Compaq 1850R PII 300 (?), being replaced with Dell 2550 PIII 800 (?) – Tokyo, JP.
Ns.apnic.net currently Dell 1550 PIII – experimenting with Cisco Local Director to have 3 Dell 1550s behind it – Brisbane, AU.
Average 406 PTR qry/sec (ns) and 606 PTR qry/sec (svc00).

7. Questions?