Domain Name Resolvers: Difference between revisions

No edit summary
Line 11: Line 11:
==ICANN and Domain Name Resolvers==
==ICANN and Domain Name Resolvers==
The mission of [[ICANN]] is to ensure protection and preservation of the stability, utility and integrity the of [[DNS]] (Domain Name System). Some alternate root operators persuade other users to have their resolvers "point" to their alternate root (which is similar to the unique authoritative root of ICANN) instead of the authoritative root. Due to the fact that pseudo-[[TLD]]s are not included and recognized by the authoritative root of ICANN, these cannot be resolved by a large number of Internet users.  
The mission of [[ICANN]] is to ensure protection and preservation of the stability, utility and integrity the of [[DNS]] (Domain Name System). Some alternate root operators persuade other users to have their resolvers "point" to their alternate root (which is similar to the unique authoritative root of ICANN) instead of the authoritative root. Due to the fact that pseudo-[[TLD]]s are not included and recognized by the authoritative root of ICANN, these cannot be resolved by a large number of Internet users.  
==ICANN and the authoritative root==
In 2001 [[ICANN]] released a policy regarding its commitment to a single authoritative root for the [[DNS]] (Domain Name System) as well as to the management of the authoritative root based on the policies created in accordance with the community processes.
There are many cases when organizations have set DBS roots as alternative roots instead of authoritative roots. Some of these alternate roots are purely experimental or operate within the norms established by the community but their common disadvantage is that these alternate roots have not been launched based on [[ICANN]] consensus processes and are not managed by [[IANA]].
Thus, [[ICANN]] must make sure that the stability of [[DNS]] is preserved even is this may lead to the limitation of alternate roots which could cause conflicts.
The [[DNS]] works based on a hierarchy. In this way, when a resolver is looking for information concerning a domain name such as "www.icannwiki.com" will have access to the resource record about ".com" of one of the root servers, which informs the resolver which computers have authoritative information about the names within the .com [[TLD]]. The resolver should next send a query to one of those authoritative ".com" nameservers asking for details regarding "icannwiki.com". A query will eventually reveal thh IP address of the computer designated by the name "www.icanwiki.com". <ref>[http://www.icann.org/en/icp/icp-3.htm ICANN and the authoritative root]</ref>


==References==
==References==
{{Reflist}}
{{Reflist}}
[[Category: Glossary]]
[[Category: Glossary]]
__NOTOC__