IPv6 doc. prefix (2001:db8::/32) - APNIC object ?
Alarig Le Lay
alarig at swordarmor.fr
Mon Mar 6 16:03:13 UTC 2017
On lun. 6 mars 10:55:18 2017, Brandon Applegate wrote:
> Just did a whois on the documentation prefix and was surprised to see what looks like a user object registered for it:
> % Information related to '2001:0DB8::/32AS132111'
> route6: 2001:0DB8::/32
> descr: FUTURE D SDN BHD
> origin: AS132111
> country: MY
> mnt-by: MAINT-FUTUREDSDNBHD-MY
> changed: hm-changed at apnic.net 20160523
> source: APNIC
> Any idea what this is ? I would have thought there might be some sanity check that would have stopped this from getting registered ?
If you look for TEST-NET-3, it is also registered to APNIC:
alarig at pikachu ~ % whois 203.0.113.1
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '203.0.113.0 - 203.0.113.255'
inetnum: 203.0.113.0 - 203.0.113.255
descr: RFC5737 Documentation Address Block
status: ASSIGNED PORTABLE
remarks: This block is reserved for use in documentation and
remarks: should not be used in any real networks.
remarks: Please see more details at
changed: hm-changed at apnic.net 20100617
address: PO Box 3646
address: South Brisbane, QLD 4101
e-mail: abuse at apnic.net
abuse-mailbox: abuse at apnic.net
auth: # Filtered
changed: hm-changed at apnic.net 20110922
role: APNIC Hostmaster
address: 6 Cordelia Street
address: South Brisbane
address: QLD 4101
phone: +61 7 3858 3100
fax-no: +61 7 3858 3199
e-mail: helpdesk at apnic.net
remarks: Administrator for APNIC
notify: hostmaster at apnic.net
changed: hm-changed at apnic.net 19981111
changed: hm-changed at apnic.net 20020211
changed: hm-changed at apnic.net 20070612
changed: hm-changed at apnic.net 20100217
changed: hm-changed at apnic.net 20101217
changed: hm-changed at apnic.net 20110815
changed: hm-changed at apnic.net 20121024
changed: hm-changed at apnic.net 20131023
% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0 (UNDEFINED)
As long as APNIC is a RIR, I don’t see a big issue with that.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the NANOG