Difference between revisions of "Domain Name Resolvers"
| Line 2: | Line 2: | ||
==Overview== | ==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 [[ISP]]s or institutional networks and | + | Simply put, 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 names 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> |
In the same way, the domain name resolvers are also viewed as the function that converts a domain name, whether private or on the public Internet, into an IP address.<ref>[http://computer.yourdictionary.com/domain-name-resolver Other domain name resolver definitions]</ref> | In the same way, the domain name resolvers are also viewed as the function that converts a domain name, whether private or on the public Internet, into an IP address.<ref>[http://computer.yourdictionary.com/domain-name-resolver Other domain name resolver definitions]</ref> | ||
| − | In order to understand the purpose and usefulness of domain name resolvers it is first required to understand the mechanism of these computers. | + | In order to understand the purpose and usefulness of domain name resolvers it is first required to understand the mechanism of these computers. |
==The mechanism of domain name resolvers== | ==The mechanism of domain name resolvers== | ||
Revision as of 21:50, 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 names related issues, which generally involves finding the corresponding IP Address.[2]
In the same way, the domain name resolvers are also viewed as the function that converts a domain name, whether private or on the public Internet, into an IP address.[3] In order to understand the purpose and usefulness of domain name resolvers it is first required to understand the mechanism of these computers.
The mechanism of domain name resolvers
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 and various components 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. This is what, basically, domain name resolvers do. This is how the domain name ICANN was just "resolved".
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. [4]
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.