From owner-freebsd-questions  Sat Oct  4 06:31:01 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA16076
          for questions-outgoing; Sat, 4 Oct 1997 06:31:01 -0700 (PDT)
Received: from jumpgate.cpn.org.au (slip6.tas.gov.au [147.109.237.41])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA16071
          for <questions@freebsd.org>; Sat, 4 Oct 1997 06:30:55 -0700 (PDT)
Received: from jumpgate.cpn.org.au (jumpgate.cpn.org.au [172.16.1.1]) by jumpgate.cpn.org.au (8.8.5/8.8.3) with SMTP id XAA00760; Sat, 4 Oct 1997 23:30:14 +1000 (EST)
Date: Sat, 4 Oct 1997 23:30:13 +1000 (EST)
From: Carey Nairn <cpn@ccd.tas.gov.au>
X-Sender: cpn@jumpgate.cpn.org.au
Reply-To: Carey Nairn <cpn@ccd.tas.gov.au>
To: questions@freebsd.org
cc: squid-users@nlanr.net
Subject: squid and 2.2.2-RELEASE
Message-ID: <Pine.BSF.3.96.971004232232.322A-100000@jumpgate.cpn.org.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

We just upgraded a 2.1.6 box to 2.2.2-RELEASE and now have problems
running squid due to DNS failures.  This is pretty wierd since DNS works
fine using nslookup etc.  The resolv.conf, host.conf, etc. is exactly the
same as our old ones, pointing to our DNS server.

Recompiling squid under 2.2.2 didn't do any good either.

This is using squid-1.1.14 and squid-1.1.16.

any thoughts?

Cheers,
Carey Nairn