This is a discussion on Re: Followup: VirtualHosts.. within the Apache Web Server forums, part of the Web Server and Related Forums category; On Sun, 12 Feb 2006 10:32:38 -0800, Evan Platt wrote: > On Sun, 12 Feb 2006 10:22:...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Sun, 12 Feb 2006 10:32:38 -0800, Evan Platt wrote:
> On Sun, 12 Feb 2006 10:22:33 -0800, Evan Platt > <evan@theobvious.espphotography.com> wrote: > >>Following up to my post a few months back, My friend finally pointed >>his IP for his domain to my server - a mac g4 running apache 2.0.52. > > Ok, rereading the reply to my original post from hansh: > "Right, the _name_ entered is passed in request header to the server > and has to match a the setting of servername -or serveralias-. > Using the IPadress, although passed to the sever- will _fail_ for > being non-distinctive between vhosts. > Thus, any domainname hosted this way must be resolved by (public) > DNS." > > Basically right now, I have a dynamic DNS. > > My domain name is a cname to phirephoto.dyndns.org. My router updates > my dyndns.org name. So when you go to mydomain.com or to the other > persons's name.com, it goes to phirephoto.dyndns.org (if that makes > sense). > > Is that the problem? No. Your router will be routing these requests from the outside world using dyndns, but internally it will be 192.168.1.2 or similar. Make sure that this is static ( no DHCP here ), and that all names resolve on this server to that IP address ( use /etc/hosts ). I recommend you use <VirtualHost *:80> only for global attributes, and then have a separate entry for www.espphotography.com and www.hisdomain.be. That way, you find out the resolution problems when you start up your web server, and not when you try and use it. ( Obviously www.espphotography.com and www.hisdomain.be are resolving externally to your dyndns address (: ) HTH, Steve |
| Thread Tools | |
| Display Modes | |
|
|