Multiple Websites using Host Header Integration to ISA server 2004/2006

I want to show you on how to publish websites using host header. in here, I used the following components:

  • Internet Information Services 6.0
  • DNS Server  to resolve different name with same IP address.
  • ISA Server 2004/2006

There are many ways to do multiple websites. in my steps, I used only one IP address with different Alias for the host headers.

Step 1: Prepare your website and upload to IIS

Figure 1:  Two websites publish

In this examples, I have 2 websites to published to the Internet. Test1 and Test2 are used with the same IP address and same ports 80.

Figure 2: Two properties of 2 websites

Step 2:  On the both properties, you see on the advanced button in Figure 2. For Test1 website,click the IP address and click Edit and add the host header value “”. repeat this at the Test2 website and give name “”

Figure 3: example of host header given.

After that, restart your IIS server.

step3: Go to your DNS server. at the Forward Lookup Zone, right-click on your domain, and Add Alias and give a Alias Name as “test1” and at Fully Qualified Domain Name (FQDN), I point to my web-server which is

Figure 4: Alias CName

please repeat this for test2 website. give alias name as

Step 4: verify that and can browse internally.

step 5: you open your ISA server and create new web server publishing on Firewall Policy. Create to allow “All” . While you go on the wizard,

at the Define Website to Publish, type the internal website. previously, the test1 website is using “”. Thus, we type in the computername/Ip address box and check the box “Forward the original host header instead of the actual one”. This is important because, it will lookup the host header that we created previous step.

Figure 5: Define Website to publish

at the select Web listener, if you don’t have at all, you need to create one web listener. Even you create multiple websites, you need one web listener and listening the same port which port 80.

after you create web listener, at Select Web Listener, click Next and at the user sets, leave it as default for all users and click Next and Finish.

* Repeat the steps for Test 2 website.

Step 6: Define your External DNS and create 2 Host Records. For example, and This is done at your public DNS or External DNS. Finally, Try to Browse..

hopefully you can work it successfully..


Web Publishing in ISA Server 2006

I would like to write about web publishing with different port.  By default, Website / IIS 6.0 is set in port 80. I now change to different port which is port 9600. I have to make sure the port is unused. you can view the port using netstat command.

Of course, in windows server 2003 environment, you need to install Internet Information Service (IIS) to publish website, or you can use apache. But, I like to use IIS.

after I installed the IIS 6.0, I need to change the port from 80 to 9600. (don’t ask me why 9600).hehehe..


Figure 1. properties of IIS

now, I go to ISA Manangement Console. Create a new website publishing on Firewall Policy.

On the publishing type, choose a “single website or load balancer. click Next.

 Figure 2. Publishing Type.

On a Server Connection Security, select the radio button like below (figure 3)






Figure 3. Server connection Security

On the Internal Publishing Detail, type the internal name site. for example, web-server. tick the box to use a computer name / ip address. for example, my web server is

just click Next for next step.

On the Public Name Details, type the public domain. let’s say (see figure 4).


 Figure 4. Public Name Details

the next configuration is the Web Listener. I need to create a web listener for this web publishing.

it’s simply straightforward, click “New” on select web listener.

   Figure 5. Web listener.

On Client Connection security, just choose Do not require SSL secure connection.

Then, the  web listener should like on Internal and External network.

 Figure 6. Web listener IP address

at the authentication setting, choose no authentication. Then proceed with next and finish.

in the Authentication Delegation, leave it as default and click Next.

At the user sets, just click Next and then Finish.

You have to alter the port number to redirect to the web server. otherwise, it will still listen to port 80. On the properties of the rule that you have created just now, go to the bridging tab and at the non-SSL port, change from 80 to 9600.

Lastly, click Apply to save the configuration.

have a try..and browse your web page.