I have a need to have a second and wholly unrelated website run on a
server with an existing site. Currently, the server is only using 1
of 2 installed NICs. There is a domain name that points to this IP
address and IIS is configured to (all unassigned) for the existing
site.
I know that there are some ramifications to using 2 NICs configured in
the same network segment, but I have no experience with this and was
wondering if I am attacking this in the wrong way. Is it possible to
connect the second NIC, get it an IP address (same subnet) and have a
domain name point to it and then in IIS seperate the 2 websites to the
actual IP address of the 2 NICs.
So I would have NIC 1 - 10.0.0.3 -
www.domain1.com
NIC 2 - 10.0.0.4 -
www.domain2.com
then in IIS i would have site1 (domain1) set to 10.0.0.3 and site2
(domain2) set to 10.0.0.4
Is that a scenario where that would work, or am I barking up the wrong
tree. I know that there are things that can be done with headers and
redirects that may also work, but wanted to see if this would be
effective.
Similar Threads
