Domain Name Resolvers: Difference between revisions
Dustin Loup (talk | contribs) No edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
==Overview== | ==Overview== | ||
The domain name resolvers cache the data and information received from users by means of queries. These resolvers are strategically located with [[ISP]]s or institutional networks and their main purpose is to respond to the user's requests related to domain names problems. These resolvers are used to resolve domain name related issues, which generally involves finding the corresponding IP Address.<ref>[http://www.icann.org/en/general/glossary.htm Domain Name Resolvers according to ICANN]</ref> | |||
==The Process== | ==The Process== | ||
In order to reach [[ICANN]], the domain name resolvers first decode the request. In this way, the request is first processed by the resolver and split into its component parts. Then, the resolver will forward the request to [[ICANN]] in order to find the corresponding IP Address. The reply is forwarded to the user's computer. | In order to reach [[ICANN]], the domain name resolvers first decode the request. In this way, the request is first processed by the resolver and split into its component parts. Then, the resolver will forward the request to [[ICANN]] in order to find the corresponding IP Address. The reply is forwarded to the user's computer. | ||
Some consider domain name resolvers a waste of time given that it would be easier to directly contact [[ICANN]]; but the resolvers maintain a high level of performance, and are essential given that it | Some consider domain name resolvers a waste of time given that it would be easier to directly contact [[ICANN]]; but the resolvers maintain a high level of performance, and are essential given that it would be very difficult for the root servers to handle billions of requests on a daily basis. <ref>[http://www.internic.net/faqs/authoritative-dns.html The Importance of Domain Name Resolver]</ref> | ||
==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 | The mission of [[ICANN]] is to ensure the protection and preservation of the stability, utility, and integrity of the [[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=== | ===ICANN and the Authoritative Root=== | ||
In 2001, [[ICANN]] released a policy regarding its commitment to a single authoritative root for the [[DNS]] as well as to the management of the authoritative root based on the policies created in accordance with the community processes. | In 2001, [[ICANN]] released a policy regarding its commitment to a single authoritative root for the [[DNS]] 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 via consensus based [[ICANN]] processes and are not managed by [[IANA]]. | 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 via consensus-based [[ICANN]] processes and are not managed by [[IANA]]. | ||
Thus, [[ICANN]] must ensure the stability of the [[DNS]] is preserved even | Thus, [[ICANN]] must ensure the stability of the [[DNS]] is preserved even if this may lead to the limitation of alternate roots which could cause conflicts. | ||
The [[DNS]] works based on a hierarchy. | The [[DNS]] works based on a hierarchy. When a resolver is looking for information concerning a domain name, such as "www.icannwiki.org", it will be given access to the resource record about ".org" by one of the root servers, which informs the resolver which computers have authoritative information about the names within the .org [[TLD]]. The resolver then sends a query to one of those authoritative ".org" nameservers asking for details regarding "icannwiki.org". A query will eventually reveal the IP address of the computer designated by the name "www.icannwiki.org". <ref>[http://www.icann.org/en/icp/icp-3.htm ICANN and the authoritative root]</ref> | ||
==References== | ==References== | ||
{{Reflist}} | {{Reflist}} | ||
[[Category: Glossary]] | [[Category: Glossary]] | ||
Latest revision as of 17:48, 19 November 2020
Domain Name Resolvers, also called DNS resolvers, are the computers which are used by ISPs to respond to a user request to resolve a domain name. "Resolving a domain name" refers to the translation of a domain name into an IP Address.[1]
Overview
The domain name resolvers cache the data and information received from users by means of queries. These resolvers are strategically located with ISPs or institutional networks and their main purpose is to respond to the user's requests related to domain names problems. These resolvers are used to resolve domain name related issues, which generally involves finding the corresponding IP Address.[2]
The Process
In order to reach ICANN, the domain name resolvers first decode the request. In this way, the request is first processed by the resolver and split into its component parts. Then, the resolver will forward the request to ICANN in order to find the corresponding IP Address. The reply is forwarded to the user's computer.
Some consider domain name resolvers a waste of time given that it would be easier to directly contact ICANN; but the resolvers maintain a high level of performance, and are essential given that it would be very difficult for the root servers to handle billions of requests on a daily basis. [3]
ICANN and Domain Name Resolvers
The mission of ICANN is to ensure the protection and preservation of the stability, utility, and integrity of the 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-TLDs 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 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 via consensus-based ICANN processes and are not managed by IANA.
Thus, ICANN must ensure the stability of the DNS is preserved even if this may lead to the limitation of alternate roots which could cause conflicts.
The DNS works based on a hierarchy. When a resolver is looking for information concerning a domain name, such as "www.icannwiki.org", it will be given access to the resource record about ".org" by one of the root servers, which informs the resolver which computers have authoritative information about the names within the .org TLD. The resolver then sends a query to one of those authoritative ".org" nameservers asking for details regarding "icannwiki.org". A query will eventually reveal the IP address of the computer designated by the name "www.icannwiki.org". [4]