We help IT Professionals succeed at work.

DNS Name resolving, Virtual Machine, IIS

gjwaite
gjwaite asked
on
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
Comment
Watch Question

Author

Commented:
Hi all from the above post, to clarify I have made sure both VM's are on the same domain. We also have a DNS server on one of our machines. I believe I have to configure the DNS servers for that domain. And do some kind of dns forwarding to the internal VM that has the website with the domain I want to ping?
DarinTCHSenior CyberSecurity Engineer
BRONZE EXPERT

Commented:
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
kevinhsiehNetwork Engineer
BRONZE EXPERT

Commented:
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.
DarinTCHSenior CyberSecurity Engineer
BRONZE EXPERT

Commented:
i guess we should have asked if these are internal web servers or publicly available

Author

Commented:
Yes, they are internal servers which are not publicly available. they are all hiding behind a firewall in my company

Author

Commented:
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)

Author

Commented:
I mean main modem not model
Network Engineer
BRONZE EXPERT
Commented:
You need additional IP addresses on your main modem/router (you will typically get 6 useable at a minimum). The other option is to put everything on a single server, use different ports for your web servers (ie. http://abc.domainB.com:8080/ {very ugly}), or use an internal proxy server which can check the host headers of the web site request and then forward the request to the correct web server (pretty complicated). Your best bet is to have an additional IP address on the modem, and then NAT/port forward that new IP to the new web server.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.