From owner-freebsd-isp  Mon Feb 10 08:01:17 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA08802
          for isp-outgoing; Mon, 10 Feb 1997 08:01:17 -0800 (PST)
Received: from main.netcorps.com (main.netcorps.com [205.149.1.66])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08795
          for <freebsd-isp@freebsd.org>; Mon, 10 Feb 1997 08:01:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by main.netcorps.com (8.7.1/8.6.12) with SMTP id HAA26941 for <freebsd-isp@freebsd.org>; Mon, 10 Feb 1997 07:59:21 -0800 (PST)
Message-Id: <199702101559.HAA26941@main.netcorps.com>
X-Authentication-Warning: main.netcorps.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: freebsd-isp@freebsd.org
Subject: Apache
Date: Mon, 10 Feb 1997 07:59:21 -0800
From: Chris Bura <chris@main.Netcorps.com>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

We've been using Apache as our web server on our BSD machines.  Everything
was fine untill about a month ago, when Apache decided it didn't want to
do hostname resolving anymore.

The load on the server wasn't that great: about 125 Virtual Hosts. Still no
more than about 12 processes running at a time.

So then we upgraded to the new version of Apache.  This ones actually has
a function where you can turn hostname resolving on or off.  We turned it
on, and nothing.  Only IP addresses.  

We installed the same Apache on another server that wasn't handling virtual
domains and it resolved the name just fine.

So has anybody found a similar problem?

Does it have to do with the number of V hosts?  Is 125 really high?

The process-wise it's definately not overloaded.

Right now we're using the actuall domain names in the virtual server 
directives.  Should we use the IP address instead?  Would that ease the
workload?

Thanks

Chris