Difference between revisions of "Domain Name Resolvers"
| Line 15: | Line 15: | ||
==References== | ==References== | ||
{{Reflist}} | {{Reflist}} | ||
| − | |||
[[Category: Glossary]] | [[Category: Glossary]] | ||
| + | __NOTOC__ | ||
Revision as of 21:55, 21 February 2011
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
Simply put, 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.
Why are resolvers so important?
Even if the process performed by domain name resolvers is easy and is for some considered as a waste of time because it would be easier to directly contact the ICANN, there is an important reason for this process: performance. More specifically, 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 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-TLDs are not included and recognized by the authoritative root of ICANN, these cannot be resolved by a large number of Internet users.