Hosting4Domain.blogspot.com

Web hosting and domain name registration are usually separate services. Although your hosting company may give or sell you a domain name with your website, most hosting companies are not domain registrars, and chances are they're procuring it from a third party. (Domain registrars often give you a website, but they're usually not "full featured" websites, and another issue.)

Managing your own domain names will usually have its biggest payoff if you should decide to get more than one domain name, a common practice that can sometimes enhance your web presence. How? Let's say, your business name is "Grumpy's Hardware and Paint." Some people know you as Grumpy's Hardware, some as Grumpy's Paint, and some as just plain Grumpy. You might want to get three domain names -- grumpyshardware.com, grumpyspaint.com, and grumpy.com -- so your site can be reached no matter what a surfer enters in his browser.

The way this would work is, you'd open your hosting account using, let's say, grumpy.com. Then you'd add on, what's called, "parked" or "mirror" domain names, grumpyshardware.com and grumpyspaint.com. Parked or mirror domains are not separate websites; they simply point to an existing website, grumpy.com, in this case.

Although the concept of a domain name may seem simple enough - using a sequence of letters and words to identify a Web address - there is a great deal more going on "behind the scenes". This is because a domain name does not represent a Web site's true address; rather, it is a mask that makes a Web site's true address easier to remember.

Domain names are actually attached to a DNS (Domain Naming System) server, which is used to translate numeric addresses (known as IP, or Internet Protocol, addresses) into words. Each site you visit on the net has a numeric IP address behind its name, which represents the site's real address on the Internet.

Every domain name must be attached to a DNS server, which is the responsibility of the domain's owner (most registrars and Web hosts will handle this issue for you). There is no one central registry for DNS information; when a user enters a domain name in to their Web browser, it is up to that URL's DNS to handle the request. The DNS server then provides the browser with the correct IP, if it exists; otherwise, it returns an error message or redirects the user elsewhere.

After an IP has been determined, the user can interact with the Web server to access specific pages. While this is a specific and complex process in itself, here is a general overview as to how it works:

1. The browser now determines which protocol (the language client machines use to communicate with servers) should be used. Examples of protocols include FTP, or File Transfer Protocol, and HTTP, HyperText Transfer Protocol.

2. The server sends a GET request to the Web server to retrieve the address it has been given. For example, when a user types http://www.example.com/1.jpg, the browser sends a GET 1.jpg command to example.com and waits for a response. The server now responds to the browser's requests. It verifies that the given address exists, finds the necessary files, runs the appropriate scripts, exchanges cookies if necessary, and returns the results back to the browser. If it cannot locate the file, the server sends an error message to the client.

3. The browser translates the data it has been given in to HTML and displays the results to the user.