The American Registry for Internet Numbers (ARIN) and ICANN are together planning changes to the infrastructure which supports the IPv4 Reverse DNS — that is, the part of the DNS which provides the ability to look up an IPv4 address and convert it to a name. The IPv4 Reverse DNS uses the special domain IN-ADDR.ARPA. [...]

{ 7 comments }

Because IPv6 is so much larger than IPv4, the IETF has been able to structure the address space more neatly.  Consequently, it is easier to distinguish between different address types based on the first few characters in the address, rather than having to refer to registry, as is often the case with IPv4. Nonetheless, there [...]

{ 0 comments }

This blog post is primarily intended to update the many people in the technical community and ccTLD community about activities related to Synchronized IDN ccTLDs. As you may know, one of the ICANN Board resolutions from the recent ICANN meeting in Nairobi directed staff to develop an extension to the Fast Track Process: a mechanism [...]

{ 2 comments }

The first four IDN ccTLD requests has just been announced as having completed the String Evaulation portion of the Fast Track Process. These are associated with: Egypt, the Russian Federation, United Arab Emirates, and Saudi Arabia. See the full announcement here: http://icann.org/en/announcements/announcement-21jan10-en.htm So what does that mean? It means that these may now initiate the [...]

{ 9 comments }

I’ve previously written about the problem with IPv4 /8s which have been used to number IP networks in an unofficial and improper way. The problem is that the unofficial usage makes it more difficult for ISPs to bring these addresses into use when they are officially allocated and so less desirable. But we have to [...]

{ 1 comment }

Some IPv4 /8s have been used to number IP networks in an unofficial and improper way. That is, they have been used without being properly allocated and registered in a public Whois database. In most cases these networks are mostly private, used internally in their organization, and so the addresses are not seen in the Internet’s routing system. The organizations using these addresses have relied on the overall availability of IPv4 addresses so that there was no pressing need to allocate all of the /8s that IANA manages. With the decreasing IANA free pool of unallocated IPv4 addresses, it is now clear that every last one of them will ultimately be allocated to the RIRs.

{ 3 comments }

In managing the root zone, recently we clarified some of the technical conformance criteria for the name servers top-level domain operators use. Before we put the adjusted criteria in place, we did some research to find out real world compliance against some of the metrics. One of the more interesting insights involved looking at network [...]

{ 2 comments }

Our new Interim Trust Anchor Repository has been launched to help people more easily deploy DNSSEC.

{ 0 comments }

Last week IANA processed a request to add AAAA records for one of the thirteen DNS root-servers.

L.root-servers.net, operated by ICANN, became the seventh of of the root servers to have it’s IPv6 address records (AAAA) added into the DNS root-zone. The addition of IPv6 service is part of ICANN’s ongoing commitment to act as a leader in enabling IPv6 services throughout the DNS.

The new IPv6 address is 2001:500:3::42

{ 11 comments }