Two steps are necessary in setting up multiple hostnames within one Umbraco installation. You must instruct the Web server to listen to the required hostnames, and then you must tell Umbraco where to redirect the request. IIS (Internet Information Services) is the Web server that Umbraco uses because it is based on .NET.
To set up your IIS website to bind to one or more hostnames, follow these instructions:
For local development and testing, you can use your Windows hosts file to set up pointers to the newly created hostnames so that they will resolve to the websites when you type them in to the browser. To do this, simply open your hosts file, located in C:WindowsSystem32driversetc, in a text editor like Notepad and add a tab-delimited entry with the IP address of your development computer and the hostname you selected in the preceding steps.
Now that IIS knows where to send the incoming requests, it's time to configure Umbraco to route those requests to the correct site as you set it up in the previous section:
If you were to take a look at the Properties tab for either homepage node now, you will find a new item called Alternative Links. This reflects the domain that you added for each of the homepage nodes, which means that the two separate sites are now available on individual domains. To illustrate that this really works, change the Site Description to see the label change between the domains, as shown in Figure 7-10.
Not only has the language changed for the two domains, but you will also notice that the culture changed so that dates, currencies, and other regionally specific values are now correct for the chosen language.
As you can see, you now have two separately accessible domains for which to serve up content in different languages. Each page needs to be translated individually and you can now assign editors and translators to each site. The next section provides an overview of the translation workflow that is built into Umbraco.