Sorry for being so new at this. It is my first time setting up or really even having more access to a server than just ftp.
So here’s what I have/did. I took an old pc I had and installed ubuntu then all the *min things. (web,user,virtual)
I have an account with DynDNS, and it does correctly go to my "server". (yay)
However, I want to create a virtual server called second2 and be able to access it from another DynDNS domain, call it second2.DynDNSdomain.net.
The problem I’m having is I can’t figure out to differentiate between the two DynDNS incoming information. They both point to my isp given ip-address. (70...* or something like that.)
I’m also behind a router (I can access)…to which the server’s ip address is always 192.168.0.194
According to virtualmin second2 virtual server’s ip address is 192.168.0.160 which I can access from my computer since I’m also on the router. The router doesn’t recognize it though.
In a nutshell I’m just trying to figure out how to get the second Dyndns domain to go to the correct virtual server.
The problem I'm having is I can't figure out to differentiate between the two DynDNS incoming information. They both point to my isp given ip-address. (70.***.**.** or something like that.)
Well, that’s the magic that Apache handles – you don’t need a unique IP for every website you wish to host.
When Firefox or IE or whatever browser you use goes to access a website, it sends a special header that includes the domain name of the site it’s trying to access.
Apache uses that header (the "host" header) to determine which domain to serve.
For your part – you’d just setup both Virtual Servers in Virtualmin, then assign your ISP given IP address to both domains in DynDNS, and make sure your router forwards port 80 and 443 to the internal web server.
So, if 192.168.0.194 is the address of your webserver, you wouldn’t need any other IP’s (for example, I’m not sure 192.168.0.160 is necessary, unless it’s an entirely different server).
Thank you! Once I put the virtual server on the same ip (192.168.0.194) and changed the domain to what it actually was on DynDNS, all worked well. Thanks again