Web Hosting and Domain Name System

Introduction Micro Widgets, Incorporated recently completed the upgrade process from Microsoft Windows Server 2008 environment to Microsoft Windows Server 2012 environment and implementation of patch management solution. Currently, mwi.com is on a third party hosting server. This is an appropriate solution, the company is still in the early stages, but it is no longer consistent with the organizational plan. This proposal addresses the process of internally hosting mwi.com on a Microsoft Windows Server 2012 server.

Begin with the protocol used to access the page. The fully qualified domain name identifies the server hosting the web page. It consists of registered domain name (second level domain name) and suffix, and these are called top level domain (TLD). Domain name is partially restricted because it is necessary to register with domain registrar. The host name consists of subdomains and domain names. Fisher has complete control over the subdomain part and can set any value to it. The URL can include path and file components, or can be changed arbitrarily by Fisher. The network domain name and path are fully managed by Fisher. For the remainder of this article we will use the term FreeURL to refer to these parts of the URL.

The naming convention for these virtual hosts is derived from the domain name. Take the following URL as an example. http://exampleSub2.exampleSub.exampleA.com/ Read the domain name from the top of the right side to the bottom of the left side. Therefore, com is TLD, exampleA is domain, exampleSub is subdomain 1, and exampleSub2 is subdomain 2. To change the host directory format recognized by lighttpd, define the mode passed to the directory where the content is located. The following table shows the host directory format used as the document root for each mode. We also use the above URL as an example of a request to indicate which host file is used for content delivery.