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

We have a website hosted on port 80 with the name Now we want to host another website on port 1111 with name and expose it to the internet. When i asked my DNS team they said they can Only redirect a domain name to the IP address and they cannot do port forwarding. Is it possible to run 2 different instances on separate ports accessible with different domai name. I have head that host header can be changed to accommodate this? Any help will be appreciated.

share|improve this question

migrated from Nov 8 '12 at 0:14

This question came from our site for professional and enthusiast programmers.

Your DNS team is correct. DNS doesn't care about the port number (except in SRV records, which doesn't matter here).

If you want both sites accessible on the same IP using IIS, you bind them both to port 80, but change the host header for each site to their FQDN. This will break SSL, though, so you can only do this with regular HTTP traffic.

If you must run them on different ports, you'll need to put a reverse proxy in front of your web server to intercept all traffic to and redirect it to your internal server on :1111

share|improve this answer

You will want to check on the Bindings for the website.

In IIS Management Console -> Sites -> the website you want on port 111 -> Right click and choose Binding -> Add binding, choose your settings and change the Port option to 1111.

share|improve this answer
This isn't going to change the requirement for the user to enter :1111 at the end of the address. – MDMarra Nov 8 '12 at 15:04

Your Answer


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