Windows Forum

Ask something
Discussion Locked

IIS/ DNS problem

0 helpful
5 replies

by cray

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am trying to setup the DNS service on my IIS server. I added a host entry to the DNS manager for our domain name(host.domain.com) and I set it up in IIS as a new web site using 'host' as the header name (since the server only has one FQDN and one IP address available for all sites). When I connect to host.domain.com it goes to domain.com and not the host website. Is there some setting that I have entered wrong or is there something else I need to do to get it to connect to one of the other sites on the server?

5 replies

by somchai

You may have a limit IP address for some reasons. But you have no limit for FQDN at all. You can assign as many of FQDN on the same server with single IP address as you like. For example, if your current server is host.domain.com with ip address 1.2.3.4. You can add up, host2.domain.com, host3.domain.com, host4.domain.com to this server. The data in DNS server may look like (I do not sure if wordwrapping in techrepublic, hope you can read it).

host IN A 1.2.3.4
host2 IN CNAME host
host3IN CNAME host
...
or
host IN A 1.2.3.4
host2 IN A 1.2.3.4
...
but I like the first style, because it is self-document that hostx point to host.

Then you can use the newly assigned host name (FQDN, of course) for new (virtual) website in IIS.

by cray

This is the way I have it setup in DNS, but instead of going to host.domain.com, host1, host2, host3 all go to the default website at domain.com instead of their respective websites (which are independant websites NOT virtual webs inside the root domain). That's my problem somthing isn't directing traffic properly on the IIS server.

by somchai

When I talk to new (virtual) website, I mean serveral websites inside the same server, that would be what you means. I does not mean virtual directory. If the websites have already created, you have to assign "host header" to each new website. The name of website created does not have the same meaning as host header. Try this, view properties of each website. click the Advanced button to assign host header.

Website for host2. assign to ip address 1.2.3.4, use host header host2.domain.com, port 80

Website for host3. assign to ip address 1.2.3.4, host header host3.domain.com, port 80

etc.

For better result, you can edit Default website and use host header of domain.com or www.domain.com based on your current DNS information.

by cray

Thank you very much. I was entering the host header name as 'host' instead of 'host.domain.com', as soon as I changed it, it worked correctly. I also was using the all unassigned as the IP address instead of explicitly using the server's static IP. Thanks for your help, Chris.

This discussion is closed to new replies.