Jump to content

Main Page: Difference between revisions

From ICANNWiki
mNo edit summary
Weekly Article - DNSSEC
Line 20: Line 20:


<br /><div style="color: #FFF; background-color: #0d8323; padding: 5px 10px; border: 1px solid #466f81;"><big>Article of the Week</big></div><div style="padding: 10px;">
<br /><div style="color: #FFF; background-color: #0d8323; padding: 5px 10px; border: 1px solid #466f81;"><big>Article of the Week</big></div><div style="padding: 10px;">
<big><b>[[Drop-Catching]]</b></big>
<big><b>[[DNSSEC]]</b></big>
<br />
<br />
[[Drop-Catching]] is the process of registering expired [[domain name]]s by means of automated systems within a short period of time (even a fraction of a second) after being canceled by the registry. Simply put, the auto-registration of domains in the moment of their deletion. Drop-Catching is performed by various companies known as "drop-catchers". The process of drop-catching is different from registering expired or new domains. The main objective of drop-catching is to secure expired domain names once these are dropped from the domain [[registry]]. This process depends on instantaneous actions, so [[domainer]]s must act as soon as possible in order to secure these domains.
The [[Domain Name System Security Extensions]] (DNSSEC) is a set of [[Domain Name System]] (DNS) extensions which enables communication authentication between hosts and DNS data, while ensuring data integrity. DNSSEC is used for securing specific information provided by DNS. The DNS was initially developed without any security extensions, thus increasing the chances to get out of synch and allow the spoofing of [[IP Address]]es with the purpose of redirecting traffic to undesired websites. DNSSEC was created as a means of adding protection and security to the DNS so that the redirected traffic could be checked and directed towards the correct server.


<strong>([[Drop-Catching|Read the full article...]])</strong>
<strong>([[DNSSEC|Read the full article...]])</strong>
<div style="float:right;"><small><strong>Related: [[Domain Name]] - [[Domainer]] - [[Registry]]</strong></small></div><div style="clear: left;"></div></div>
<div style="float:right;"><small><strong>Related: [[DNS]] - [[RFC]] - [[IP Address]]</strong></small></div><div style="clear: left;"></div></div>


<br /><div style="color: #FFF; background-color: #466f81; padding: 5px 10px; border: 1px solid #0d8323;"><big>Latest Feature</big></div><div style="padding: 10px;">
<br /><div style="color: #FFF; background-color: #466f81; padding: 5px 10px; border: 1px solid #0d8323;"><big>Latest Feature</big></div><div style="padding: 10px;">

Revision as of 23:28, 26 May 2014

ICANNWiki is a nonprofit organization. Learn more about supporting our mission by downloading the
ICANNWiki Info Sheet

Many thanks to our sponsors for all of their continued support!

Neustar  

ICANN

Google
Amazon  Radix

Dominios LatinoaméricaRegistry.Africa  

Afilias  Public Interest Registry

 Donuts   FairWinds Partners

SSIG  Allegravita  

 Freund & Brackey 

Sponsorship


Article of the Week

DNSSEC
The Domain Name System Security Extensions (DNSSEC) is a set of Domain Name System (DNS) extensions which enables communication authentication between hosts and DNS data, while ensuring data integrity. DNSSEC is used for securing specific information provided by DNS. The DNS was initially developed without any security extensions, thus increasing the chances to get out of synch and allow the spoofing of IP Addresses with the purpose of redirecting traffic to undesired websites. DNSSEC was created as a means of adding protection and security to the DNS so that the redirected traffic could be checked and directed towards the correct server.

(Read the full article...)

Related: DNS - RFC - IP Address


Latest Feature

Name Collision
A Name Collision describes the circumstance in which a term attempting to reach a private Domain Name results in resolving to a public Domain Name unintentionally. Private domain names are used in Intranets and in many corporations and organizations throughout the world. A domain name on a private network that matches a name in the public Internet can create security risks, confusion, and systems failure. Although the Name Collision issue is not new, a renewed interest in the issue came about in 2013 as ICANN's New gTLD Program was preparing to delegate hundreds of new domain names to the Root Zone. The topic was debated fiercely within the ICANN community when a report by Interisle Consulting was prepared for and released by ICANN.

(Read the full article...)

 

ICANNWiki currently has 8,703 articles.