Just a WAG here (you're already doing more with apache than I've been
able to play with ;-), but isn't ServerName what Apache is expecting in
a "Host:" header from the requesting browser as the site name. So I
would think you would want "travelcruise" (assuming your registered the
domain obviously).  Although from reading the docs on name-based virtual
hosts, 
http://www.apache.org/docs/vhosts/name-based.html

since you're using a different IP address for this virtual host, than
this section is the primary vhost for that IP, and will be returned
regardless of what "host:" header is sent.  It'll only get you into
trouble if you were to put another name-based vhost in with the same IP
address, iow if the server names weren't fixed the travelcruise would
always be returned.

The neat thing about vhosts is that you could have only 1 public IP
address, and support many different sites off the same rig just using
different ServerName variables for each site's VirtualHost section.  At
least I think it's neat, any drawbacks or limitations on this?

> Charlie Bullen wrote:
> <VirtualHost 63.226.30.195>
>  ServerAdmin webmaster@travelexecutives.com
>  DocumentRoot /home/groups/travelcruise
>  ServerName microserver.travelexecutives.com
>  ErrorLog logs/travelcruise.com-error_log
>  TransferLog logs/travelcruise.com-access_log
>  </VirtualHost>microserver.travelexecutives.com
> 
> 
> What is not clear is should I keep the servername the same for all =
>  domains, namley microserver.travelexecutives.com
>  or should I change it to microserver.travelcruise.com ?
> 
> Regards,
> 
> Charlie