Followup: Squid v1.0/v1.0.1 problems under OSF/1

>Hi all,
> Has anyone noted problems with the later versions of Squid running
>under OSF/1, we've runn the earlier beta's successfully on this platform
>since early harvest days ... but the latest versions give 'connect failed'
>messages on nearly all retrievals.
>
> This seemed to start first with cgi related requests, but is now on
>all!
>
> Any notices of problems appreciated ...

OK ... I've had time to do a few more tests, and the behaviour I observe is
that the DNS request for addresses seems to be returning garbage addresses
for lookups. For example, user requests www.microsoft.com, squid farms
this out to the dnsserver, the dnsserver process returns 255.255.255.255,
squid then proceeds to attempt to connect to 255.255.255.255:80, thereby
getting a connect failed/refused.

I've examined some of the source to dnsserver and built a copy on another
OSF1 box (which worked BTW on my box, but refused to start with -t as an
option). How do I start the dnsserver processes correctly in debugging mode?

The cachemgr reports each address as '255.255.255.255 0 0' ... BTW, this
machines name resolution does work outside of squid, it's one of our DNS
servers.

Anybody got an other ideas ...

--
Craig
                            ,,,   Wot, NO mountains!
 ======================oOO=(o o)=OOo===================================
  Craig Morgan              (_)      Senior Lecturer, CS Group
  School of Computing                Email: C.Morgan@soc.staffs.ac.uk
  Staffordshire University           Phone: +44 (0)1785 353466
  Beaconside                         Fax:   +44 (0)1785 353497
  Stafford, UK  ST18 0DG             Pager: +44 (0)839 453754
  "It's the downhill thrills, that make the uphill slog worthwhile..."
 ======================================================================