Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For the sake of keeping it simple, let's say I have 2 sites on my VM. The first site is and the second site is Here's my IIS on the server:

enter image description here

Focusing on, here are the site bindings:

enter image description here

The IP address is the internal IP for the server. I have a simple index.html page for testing located in the root directory. Here's where I have my web content for my sites, which I've appropriately mapped to in IIS:

enter image description here

Finally, I configured my DNS settings for as having an A record (*) that points to the public IP for my web server. When this is set like this, accessing the website brings up the content under Default Web Site in IIS. So, I would imagine I need to do something like * instead of a wildcard *. I tried this but I get an "Unresolved DNS error", even after waiting the propagation period. Here's my DNS:

enter image description here

QUESTION: I want to obviously host multiple sites on one IP. Am I following the correct path? Anything you see off hand that I'm doing wrong? I feel like I need to be doing something else in IIS.

share|improve this question
The name of the IIS feature escapes me at the moment, but don't you need something like an .htaccess to define virtual sites? – tombull89 Jul 17 '13 at 14:23
Never heard of needing that, but I'm new to this, so that doesn't mean anything :) – Mike Marks Jul 17 '13 at 14:24
Does it work if you add a CNAME for "www" as the hostname and point it to "" as the address? – Nathan C Jul 17 '13 at 14:24
I need to route both and to the same place, and from my research doing a CNAME you can't use wildcards. So, while www may work, it'll only work if the user does and will not work if they do Does this make any sense? @NathanC – Mike Marks Jul 17 '13 at 14:26
Have a quick read of and see if that clears your issue up a bit. – tombull89 Jul 17 '13 at 14:27
  1. DNS doesn't propagate.

  2. Create an A record for and for that resolves to your public ip address.

  3. Add to the web site bindings for the boxfetch web site.

  4. Do the same thing for the other web site.

share|improve this answer
So are you saying that DNS changes are automatic? I added 2 Host A records, one for and one for, pointed to the public IP. I went to the site bindings, and changed the Host Name from to for the binding on port 80. Still same problem. – Mike Marks Jul 17 '13 at 15:05
Correction, now works but doesn't work. – Mike Marks Jul 17 '13 at 15:06
DNS records don't propagate. If you create a new DNS record it is available immediately to all hosts that request it. If you update a record then those hosts that have that record cached will wait until the TTL of the record expires before looking up the record again. At no time do your DNS records get propagated. They get cached, but only by hosts that request them. - Make sure that and point to the public ip address that gets "forwarded" to your internal web server ip address. Then stop and restart IIS and try them both again. – joeqwerty Jul 17 '13 at 15:16
Ugh, I tried all this, same problem. dns_server_failure. – Mike Marks Jul 17 '13 at 15:33
A check of the domain at DnsStuff shows no A record for the naked domain name and no A record for You need to check your DNS records again. – joeqwerty Jul 17 '13 at 15:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.