Skip Navigation

Close and don't show again.

Your browser is out of date.

You may not get the full experience here on National Journal.

Please upgrade your browser to any of the following supported browsers:

Reveal Navigation

ICANN Explains Domain Name Database Glitch;Outage Continues ICANN Explains Domain Name Database Glitch;Outage Continues ICANN Explains Domain Name Database Glitch;Outage Continues ICANN Explains Domain Nam...

share
This ad will end in seconds
Close X

Not a member? Learn More »

Forget Your Password?

Don't have an account? Register »

Reveal Navigation

 

Congress

ICANN Explains Domain Name Database Glitch;Outage Continues

April 20, 2012

The organization that manages the Internet's domain name system said on Friday it is trying to make sure it has completely solved a technical glitch that shut down a database for applicants wanting to register new top-level domain names.

"What we are trying to do is do it right, instead of trying to do it fast," Jeff Moss, chief security officer for the Internet Corporation for Assigned Names and Numbers, said in an online video.

The new generic top-level domain names will greatly expand the current 23-member universe of dot-coms and dot-orgs to dot-just-about-anything.

The database was shut down after users noticed they could see information from other applicants. That was due to a problem in the way files were being deleted, Moss said, and shutting down the whole system was the most prudent action.

He said there is no evidence of a cyberattack or any indication that any private information was compromised. Still, ICANN is taking steps to document exactly who may have seen what data, in order to avoid any "monkey business," Moss said.

In January ICANN launched the system for registering new top-level domain names, such as .bank or .anything. Critics seized on the technical problems as evidence that ICANN is not up to the task of managing the process, but Moss argued that the organization is exercising caution by proceeding with tests on the solution to the problem before re-launching the database.

Get us in your feed.