Service announcement: Reverse DNS Zone update
Start Time | Monday, 29 July 2019 09:00 (UTC +10) |
End Time | Monday, 05 August 2019 10:00 (UTC +10) |
Duration | 8 Days |
Services affected | APNIC Reverse DNS zones |
Description | On Monday, 29 July 2019, the APNIC Infrastructure Services team will start the process of migrating existing DNSSEC keys on its Reverse DNS zones from RSA to ECDSA. This process involves a DNSSEC rollover that will last for several days. For the duration of the migration, it is expected that DNS responses from affected zones will increase in size due to the presence of multiple DNSKEYs and RRSIGs. Reverse DNS updates will continue to work as normal and we are not expecting DNSSEC validation failure during the migration. By 5 August 2019, the parent zones of APNIC’s reverse DNS will be updated with the new ECDSA DS record. Affected Reverse DNS zones: |RDNS zones |Current KEYS | Future KEYS | |101.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |103.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |106.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |110.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |111.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |112.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |113.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |114.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |115.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |116.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |117.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |118.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |119.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |120.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |121.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |122.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |123.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |124.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |125.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |14.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |150.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |153.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |163.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |171.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |175.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |180.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |182.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |183.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |1.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |202.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |203.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |210.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |211.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |218.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |219.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |220.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |221.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |222.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |223.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |27.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |36.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |39.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |42.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |43.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |49.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |58.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |59.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |60.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |61.in-addr.arpa |RSASHA1 |ECDSAP256SHA256| |0.4.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |2.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |3.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |4.4.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |5.4.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |9.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |a.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |b.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |c.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |d.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |e.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |f.0.1.0.0.2.ip6.arpa |RSASHA1 |ECDSAP256SHA256| |
We apologize for the loss of facilities and any inconvenience caused. Should you require assistance in dealing with any problems arising from this outage, please contact the APNIC Helpdesk.