gjwaite
asked on
DNS Name resolving, Virtual Machine, IIS
We have (lets call it webA) website that is configured under IIS on a virtual machine internally. On our registrar console for the domain it points to our routers ip address. However when i ping that domain(lets call it xyz.domain.com) it pings to the machine ipaddress that has the website with the hostheader(which has the domain we need xyz.domainA.com). This works fine as i when i access the website http://xyz.domainA.com i am able to access the website
Now I have set up a different domain(abc.domainB.com) on our registrars console(like1and1.com). I have set up the A-record IP address to point to the routers ip address to. However I understand I have to change some additional configuration on that VM,so that i can configure a website running on that virtual machine(different virtual machine from the previous) to have the host header abc.domainB.com. However when i ping the domain, it just pings our router. How do I make it access the website in the VM.
I have turned off windows firewall. The first domain is for a website running on windows 2003 server.
the other one runs on windows 2008 server
Now I have set up a different domain(abc.domainB.com) on our registrars console(like1and1.com). I have set up the A-record IP address to point to the routers ip address to. However I understand I have to change some additional configuration on that VM,so that i can configure a website running on that virtual machine(different virtual machine from the previous) to have the host header abc.domainB.com. However when i ping the domain, it just pings our router. How do I make it access the website in the VM.
I have turned off windows firewall. The first domain is for a website running on windows 2003 server.
the other one runs on windows 2008 server
if they are in the same domain as the DNS server just setup a simple Host A record pointing to the IP address you want
also probably a reverse record for IP to Name resolution
also probably a reverse record for IP to Name resolution
As I understand it you have two different machines (VMs, but that isn't important) which are hosting two different web sites.
You seem to indicate that the router has only one IP address. This won't work, because the router needs to have a different IP address for each web server. Your router doesn't know about host headers, so it can't use them to send traffic to the correct web server.
If both web sites were on the same machine, then you could use host headers on the server to serve up the content of multiple websites from a single server using a single IP address.
You seem to indicate that the router has only one IP address. This won't work, because the router needs to have a different IP address for each web server. Your router doesn't know about host headers, so it can't use them to send traffic to the correct web server.
If both web sites were on the same machine, then you could use host headers on the server to serve up the content of multiple websites from a single server using a single IP address.
i guess we should have asked if these are internal web servers or publicly available
ASKER
Yes, they are internal servers which are not publicly available. they are all hiding behind a firewall in my company
ASKER
Sorry guys so we have a main model (with an ip address lets say A) This passes through a firewall. before coming internally.
All the machines hide behind the firewall (fortigate machine from which i have an admin console etc to forward traffic I believe)
Our A-record points to the ip address of this model(ip address A which is static)
All the machines hide behind the firewall (fortigate machine from which i have an admin console etc to forward traffic I believe)
Our A-record points to the ip address of this model(ip address A which is static)
ASKER
I mean main modem not model
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER