Date: Fri, 28 Mar 2003 17:03:05 -0500 From: Phillip Smith <phillip.smith@sympatico.ca> To: <freebsd-questions@freebsd.org> Subject: NameVirutalHost on multiple IPs not working?? Message-ID: <BAAA30C9.3A99%phillip.smith@sympatico.ca>
next in thread | raw e-mail | index | archive | help
Hi, I'm having a challenge with my Apache NameVirtualHost config... I have my server connected to two networks, AT&T and UUNET, the NIC is assigned a AT&T IP and is aliased which several others, both AT&T and UUNET. That part is working well. When a client requests a site, our DNS returns two IP addresses, one AT&T and one UUNET. (I don't want to discuss the quality of this solution (grin), just why it's not working at the moment.) The idea is that if one network is down, the person's web client should look for the domain at the second IP (I know this isn't 'redundant,' but it's what i got) Now, the VirtualHosts on AT&T are working fine. I have domains pointing to 219 and 220 (below) and Apache handles them perfectly. But, if AT&T goes down, Apache only returns the 'default' VirtualHost on 107 and 108, not the client's site. Here's what I have in the relevant parts of httpd.conf NameVirtualHost 123.456.789.219 (AT&T) NameVirtualHost 123.456.789.220 (AT&T) NameVirtualHost 123.456.789.107 (UUNET) NameVirtualHost 123.456.789.108 (UUNET) Then a standard directive would be <VirtualHost www.clientdomain.com> ServerAdmin me@whatever.com DocumentRoot /www/clientname ServerName www.clientdomain.com ..yadda yadda </VirtualHost> FreeBSD 4.6 Apache 1.2.x (11 i think) Is there something that I'm missing? phillip. P.S. Please cc me directly, as I'm temporarily not subscribed to the list.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAAA30C9.3A99%phillip.smith>