Tuesday, July 20, 2010
The Domain Name System (DNS) helps users to reach different sites on the Internet. Every computer on the Internet has an exclusive address that consists of series of complex numbers. It is called its "IP address". IP stands for "Internet Protocol". Remembering everyone's IP address is difficult. The DNS helps users to remember the address with help of group of letters i.e. the "domain name" to be used instead. So instead of typing 192.0.34.65, you can type www.icann.org. This is like a memory aid that helps in remembering the addresses. Converting the name into the IP address is called "resolving the domain name." The aim of the DNS is for any Internet user worldwide to log on to a specific website by entering its domain name. Domain names are also used for reaching e-mail addresses and for other Internet applications."Universal resolvability" and its significance
The DNS works just like a telephone number that is unique in itself. Domain names being exclusive can be accessed globally, and everyone wanting to connect to that domain name will be able to reach it. Thus it is exclusive and reliable like any phone number. "Universal resolvability" is ensuring predictable results from any place on the Internet. This significant design feature of the DNS makes the Internet resourceful and very useful. The DNS helps you send an email to the right person. Each IP address will have its own distinctive domain name.What is ICANN?
ICANN is the global, non-profit, private-sector coordinating body performing on behalf of public interest. ICANN makes sure that the DNS continues to work efficiently - by supervising the distribution of unique numeric IP addresses and domain names. ICANN also manages the processes and systems that ensure that each domain name maps to the correct IP address. ICANN is responsible for managing and coordinating the DNS to ensure universal resolvability.Workings behind the scenes
In an Internet address - such as icann.org - the .org part is called the Top Level Domain, or TLD; the "TLD registry" organizations contain online databases with information about the domain names in that TLD. The .org registry database, for instance, contains the Internet whereabouts - or IP address - of icann.org. So in trying to find the Internet address of icann.org your computer has to first search the .org registry database.
The center of the DNS contains 13 special computers, called root servers. ICANN coordinates them and are distributed around the world. All 13 contain the same important information - this is to spread the workload and back each other up. The root servers have the IP addresses of all the TLD registries - the global registries such as .com, .org, etc. and the 244 country-specific registries such as .fr (France), .cn (China), etc. This is critical information. If the information is not 100% correct or if it is unclear, it might not be possible to locate a key registry on the Internet. In DNS jargon, the information must be unique and authentic.How is this information used?
Spread across the Internet are thousands of computers - called "Domain Name Resolvers" or just plain "resolvers" - that routinely store the information they receive from queries to the root servers. These resolvers are strategically located with Internet Service Providers (ISPs) or institutional networks. They are used to respond to a user's request to find the corresponding IP address.What happens to a user's request to reach at icann.org?
The request is first sent to a local resolver. The resolver splits the request into its component parts. It finds the .org registry and forwards the request over to the .org registry to find the IP address of icann.org. This answer is forwarded back to the user's computer.
Why do we need the resolvers? There is a reason why we can't we use the root servers directly even though they contain almost all of the same information. Performance is the reason why. The root servers will not be able to handle billions of requests coming its way every day and thus would slow users down.
Now we will talk about the remaining part of the complicated name… www.icann.org. To begin with the DNS is a hierarchical system. First, the resolver finds the IP address for the .org registry, then asks that registry to find the IP address for icann.org and lastly goes on to a local computer at that address to find the final IP address for www.icann.org. The root servers play an important role storing information about the unique root. There would be much confusion if there were multiple TLDs with the same name. How would we know which the user intends to use. However, the beautiful architecture of the Internet ensures that is a unique and authoritative root to avoid confusion.What can ICANN do?
ICANN's mission is to protect and preserve the stability, integrity and utility of the global Internet community, the DNS and the authoritative root ICANN was actually established to manage. ICANN truly has no responsibility towards the alternate roots as long as to do not destabilize the DNS or harm the strength of the authoritative root. However, what ICANN does do is educate and inform us about threats to the Internet's reliability and stability. ICANN is therefore a unanimous development body for the global Internet community. It's focus is the development of consesus policies relating to the single authoritative root and the DNS as well those that allow the systematic introduction of new TLDs.
SOURCE:http://www.webhostingsearch.com/articles/all-about-domains.php
The DNS works just like a telephone number that is unique in itself. Domain names being exclusive can be accessed globally, and everyone wanting to connect to that domain name will be able to reach it. Thus it is exclusive and reliable like any phone number. "Universal resolvability" is ensuring predictable results from any place on the Internet. This significant design feature of the DNS makes the Internet resourceful and very useful. The DNS helps you send an email to the right person. Each IP address will have its own distinctive domain name.What is ICANN?
ICANN is the global, non-profit, private-sector coordinating body performing on behalf of public interest. ICANN makes sure that the DNS continues to work efficiently - by supervising the distribution of unique numeric IP addresses and domain names. ICANN also manages the processes and systems that ensure that each domain name maps to the correct IP address. ICANN is responsible for managing and coordinating the DNS to ensure universal resolvability.Workings behind the scenes
In an Internet address - such as icann.org - the .org part is called the Top Level Domain, or TLD; the "TLD registry" organizations contain online databases with information about the domain names in that TLD. The .org registry database, for instance, contains the Internet whereabouts - or IP address - of icann.org. So in trying to find the Internet address of icann.org your computer has to first search the .org registry database.
The center of the DNS contains 13 special computers, called root servers. ICANN coordinates them and are distributed around the world. All 13 contain the same important information - this is to spread the workload and back each other up. The root servers have the IP addresses of all the TLD registries - the global registries such as .com, .org, etc. and the 244 country-specific registries such as .fr (France), .cn (China), etc. This is critical information. If the information is not 100% correct or if it is unclear, it might not be possible to locate a key registry on the Internet. In DNS jargon, the information must be unique and authentic.How is this information used?
Spread across the Internet are thousands of computers - called "Domain Name Resolvers" or just plain "resolvers" - that routinely store the information they receive from queries to the root servers. These resolvers are strategically located with Internet Service Providers (ISPs) or institutional networks. They are used to respond to a user's request to find the corresponding IP address.What happens to a user's request to reach at icann.org?
The request is first sent to a local resolver. The resolver splits the request into its component parts. It finds the .org registry and forwards the request over to the .org registry to find the IP address of icann.org. This answer is forwarded back to the user's computer.
Why do we need the resolvers? There is a reason why we can't we use the root servers directly even though they contain almost all of the same information. Performance is the reason why. The root servers will not be able to handle billions of requests coming its way every day and thus would slow users down.
Now we will talk about the remaining part of the complicated name… www.icann.org. To begin with the DNS is a hierarchical system. First, the resolver finds the IP address for the .org registry, then asks that registry to find the IP address for icann.org and lastly goes on to a local computer at that address to find the final IP address for www.icann.org. The root servers play an important role storing information about the unique root. There would be much confusion if there were multiple TLDs with the same name. How would we know which the user intends to use. However, the beautiful architecture of the Internet ensures that is a unique and authoritative root to avoid confusion.What can ICANN do?
ICANN's mission is to protect and preserve the stability, integrity and utility of the global Internet community, the DNS and the authoritative root ICANN was actually established to manage. ICANN truly has no responsibility towards the alternate roots as long as to do not destabilize the DNS or harm the strength of the authoritative root. However, what ICANN does do is educate and inform us about threats to the Internet's reliability and stability. ICANN is therefore a unanimous development body for the global Internet community. It's focus is the development of consesus policies relating to the single authoritative root and the DNS as well those that allow the systematic introduction of new TLDs.
SOURCE:http://www.webhostingsearch.com/articles/all-about-domains.php
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment