RE: [SQU] Unable to connect to/resolve internal addresses

Hi,

I believe the main reason for my problems is below:

Changes to version 2.3.DEVEL3
domain name matching The function which checks for a match between a hostname and a domain name has been rewritten, and its behavior is now slightly different. Previously, the domain ``com'' would match the hostname ``foo.com'', but this is no longer the case. Now, if you must write ``.com'' to match ``foo.com''.

That is the missing dot in front of the domain name . When I prepended the domains that I previously specified with a dot it worked . I have used the dstdomain like this

acl local-intranet printer test.se test2.se test3.se
always_direct allow local-intranet

That does not work, but

acl local-intranet printer .test.se .test2.se .test3.se

works .

Thanks for the help !

/Anders

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@hem.passagen.se]
Sent: den 15 december 2000 05:54
To: Anders Strandberg (EPL)
Cc: Anders Strandberg (EPL); squid-users@ircache.net
Subject: Re: [SQU] Unable to connect to/resolve internal addresses

Anders Strandberg (EPL) wrote:
>
> Hello,
>
> I think that it recieves the 205 error from the parent cache.
> ----
> ERROR 205 -- DNS name lookup failure. Please contact your system administrator.
>
> This means that:
>
> cacher
> ----

Sure looks like an NetApp error message from one of the ericsson gateway
proxies. So it smells like something is wrong with the always_direct
settings.

But I think there is also a small issue with ICMP in Squid-2.3 that
might under some specific conditions confuse Squid. Also generally I
find that ICMP probing support in Squid is only a waste of resources. Is
there any specific reason to why you have enabled it?

--
Henrik Nordstrom
Squid Hacker
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html