Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 75
  • Last Modified:

2 websites hosted on premise

I have 2 webistes hosted on-premise. Can I point to both of them using the same outside IP, or would each require their own IP address?
0
Philip Thomas
Asked:
Philip Thomas
1 Solution
 
giltjrCommented:
Simple answer, they each need their own IP address.

More complex answer, if you don't mind specifying a port number on one of them (http://host1.domain.com and then http://host2.domain.com:81) and your firewall can do port mapping, then you can share IP address.  If you had a layer 7 load balancer or a reverse proxy server, you could also share an IP address and the balancer can send to the correct host based on the host name.
0
 
Dr. KlahnPrincipal Software EngineerCommented:
Using Apache,as many sites as you wish can be hosted on one IP address using the VirtualHost option.  Incoming HTTP requests are sorted by the web site name in the request header, and then "routed" to the correct vhost.

Note that there are a few restrictions associated with this.  One is that all sites must be running in the same server process, and the other is that if secure HTTP is used, the use of HTTPS must be uniform across all vhosts.

NameVirtualHost *:80
# This VirtualHost is used for requests with no server name.
<VirtualHost *:80>
DocumentRoot /www/localhost
#                    (www).example1.com
<VirtualHost *:80>
ServerName www.example1.com
ServerAlias example1.* www.example1.*
UseCanonicalName on
DocumentRoot /www/example1
</VirtualHost>
#                    (www).example2.com
<VirtualHost *:80>
ServerName www.example2.com
ServerAlias example2.* www.example2.*
UseCanonicalName on
DocumentRoot /www/example2
</VirtualHost>

Open in new window

1
 
giltjrCommented:
If you are using IIS (which you imply that you are) IIS calls Virtual Hosts Host Headers.  This only works if both sites are hosted on the same IIS Server.  I was assuming that you had 2 separate IIS servers.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
Dan McFaddenSystems EngineerCommented:
You can host hundreds of sites on a single IP is you specifically binding all sites to the same IP address AND you must then use the host names fields on each site binding.  The host name must match the FQDN that is resolvable in DNS.

Dan
0
 
Philip ThomasMIS ManagerAuthor Commented:
Yes, both sites are on the same IIS server.
0
 
Dan McFaddenSystems EngineerCommented:
So, very easy to setup.


1. In DNS, make sure that each website has a resolvable Full Qualified Domain Name  (FQDN/URL) that points to the single IP on the server.

For Example:
Server IP = 1.2.3.4
Website A Name = www.domainA.com
Website B Name = www.domainB.com

In DNS, under domainA.com, there should be (at least) an A Record that point www to 1.2.3.4.  So when you do an NSLOOKUP, you should resolve www.domainA.com to 1.2.3.4 or you should resolve 1.2.3.4 to www.domainA.com.  This is the same for domainB.com.

2. On the binding for each site, specifically choose the IP Address from step 1, and fill out the Host Name field to match the FQDNs that are resolvable in DNS.

Dan
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now