This is a courtesy notification of an upcoming change to the nameserver set for the IN-ADDR.ARPA zone.
\nThere is no expected impact on the functional operation of the DNS due to this change.
\nThere are no actions required by DNS server operators or end users.<\/p>\n
For more information about this work, please see http:\/\/in-addr-transition.icann.org\/<\/a><\/p>\n DETAIL<\/strong><\/p>\n The IN-ADDR.ARPA zone is used to provide reverse mapping (number to name) for IPv4. The servers which currently provide authoritative DNS service for the IN-ADDR.ARPA zone are as follows:<\/p>\n On Wednesday 2010-02-16 processing will begin to change the nameserver set to the following, as described in RFC 5855:<\/p>\n The usual IANA process for a change in the ARPA zone involves a series of technical checks and the gathering of various authorisations, and may take several days to complete.<\/p>\n Following this, the IN-ADDR.ARPA zone will be dropped from root servers in two groups:<\/p>\n Individual root server operators will choose a time for the maintenance within their respective window and follow their usual procedures to carry out the change.<\/p>\n Courtesy notification will be sent to this list once this change has been fully implemented.<\/p>\n Regards,<\/p>\n","protected":false},"excerpt":{"rendered":" This is a courtesy notification of an upcoming change to the nameserver set for the IN-ADDR.ARPA zone. For more information about this work, please see […]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[],"_links":{"self":[{"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/posts\/1309"}],"collection":[{"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/comments?post=1309"}],"version-history":[{"count":6,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/posts\/1309\/revisions"}],"predecessor-version":[{"id":2857,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/posts\/1309\/revisions\/2857"}],"wp:attachment":[{"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/media?parent=1309"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/categories?post=1309"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dns.icann.org\/wp-json\/wp\/v2\/tags?post=1309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
\n
There is no expected impact on the functional operation of the DNS due to this change.
There are no actions required by DNS server operators or end users.<\/p>\n