Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I'm not an admin so this may seem to be a very simplistic question. Currently, I have ten ASP.NET Web Forms sites on a W2K8 hosted VM - I manage it myself. Right now, all the sites have the same server IP address and I want to change this so that each site has its own IP (that with which they were originally registered). Initially, I used the server IP when setting the bindings - I'm guessing that IIS set these as host headers?

What are the steps involved in setting this up in IIS? Do I have to change the way email is configured in all the individual Web.Config files? (currently mailing from server IP mail host).

share|improve this question
up vote 4 down vote accepted

Generally what you need to do is:

  1. Assign the extra IPs to the network adapter properties in the Control Panel.
  2. Edit the bindings in IIS like in the image below (the IP Address dropdown) enter image description here

  3. Change your A records to reflect the new IP address for each website on your DNS server.

share|improve this answer
Not sure what you mean by #3... I thought I could get the registered IPs for each site and assign them as in steps #1 and #2. Are you saying I have to log into the clients' registrar accounts and update something there? – IrishChieftain Sep 28 '11 at 22:28
No you don't need to change anything at the domain's registrar, rathen on the nameservers their configured to point at. – George Tasioulis Sep 28 '11 at 22:31
For example if has the nameservers and then you need to go into the DNS zone of those two nameservers and change the A record that points from the current IP (let say to the new IP you will assign it to (eg. – George Tasioulis Sep 28 '11 at 22:33
Yes, they're definitely configured since they're live. BUT: They're configured to point to IP A, now if you go and assign them a new IP under IIS ie IP B, you also need to change that on the nameserver, so that he directs the queries to the new IP. – George Tasioulis Sep 28 '11 at 22:37
Keep in mind that changing a domains IP address can take between 24-48 hours to propagate around the internet (depending on the TTL value). This is called TTL caching or propagation and here's a link that explains how you can speed it up link – George Tasioulis Sep 28 '11 at 22:41

You want to assign each IP to the NIC in the Control Panel. After that, you edit the bindings in IIS like you mentioned. That should be all that you need to know. You shouldn't have to change your web.configs.

share|improve this answer

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.