Dyndns and apache

[Peter Boy]

Am Sonntag, den 21.08.2005, 14:18 +0100 schrieb Paul F. Johnson:
> Hi,
> 
> On Sun, 2005-08-21 at 15:13 +0200, Peter Boy wrote:
> 
> > Did you try
> >   <VirtualHost 82.42.51.231:80> 
> > or (better)
> >   <VirtualHost *:80>
> > instead?
> 
> Problem with that is that there are multiple domains on the server and
> having both set as *:80 causes a conflict.

Should not. The setting ing <VirtualHost ...> referrs to the interface
afaik. If you host several virtual domains you should active name base
virtual server by name (you did that if remember correctly) Then the
different virtual hosts are identified by the ServerName directive.

>From the apache doku:


To use name-based virtual hosting, you must designate the IP address
(and possibly port) on the server that will be accepting requests for
the hosts. This is configured using the NameVirtualHost directive. In
the normal case where any and all IP addresses on the server should be
used, you can use * as the argument to NameVirtualHost. If you're
planning to use multiple ports (e.g. running SSL) you should add a Port
to the argument, such as *:80. Note that mentioning an IP address in a
NameVirtualHost directive does not automatically make the server listen
to that IP address. See Setting which addresses and ports Apache uses
for more details. In addition, any IP address specified here must be
associated with a network interface on the server.

The next step is to create a <VirtualHost> block for each different host
that you would like to serve. The argument to the <VirtualHost>
directive should be the same as the argument to the NameVirtualHost
directive (ie, an IP address, or * for all addresses). Inside each
<VirtualHost> block, you will need at minimum a ServerName directive to
designate which host is served and a DocumentRoot directive to show
where in the filesystem the content for that host lives.


The <virtualHost> directive does expect an IP number or an *


So, the problem must be burried elsewhere.

Maybe it is a better way to inspect the error messages which come up
when you configure it as the apache manual suggests.


Regards
Peter