[squid-users] Resolving non-FQDN names

[Jeff Jenkins]

I am running squid2.5.STABLE10.  When a client specifies a non-FQDN  
name  ("foo", instead of "foo.goo.com"), squid fails to resolve the  
name.   The machine squid is running on is configured to use DNS  
servers that can resolve that name.  I can do nslookups on foo on the  
squid host machine w/o failures.


Is there some config that controls this?

Thanks!

-- jrj

Re: [squid-users] Resolving non-FQDN names

[Jeff Jenkins]

I think I found it:

httpd_accel_with_proxy on

-- jrj

On Sep 5, 2008, at 9:33 AM, Jeff Jenkins wrote:

I am running squid2.5.STABLE10.  When a client specifies a non-FQDN  
name  ("foo", instead of "foo.goo.com"), squid fails to resolve the  
name.   The machine squid is running on is configured to use DNS  
servers that can resolve that name.  I can do nslookups on foo on  
the squid host machine w/o failures.


Is there some config that controls this?

Thanks!

-- jrj

Re: [squid-users] Resolving non-FQDN names

[Amos Jeffries]

> I think I found it:
>
> httpd_accel_with_proxy on


You would do much better upgrading to a newer squid if you are going to
use the reverse-proxy features. The 2.5 ones are badly done.

The real fix you are looking for is the 'search' or 'domain' options when
configuring /etc/resolv.conf

Amos

>
> -- jrj
>
> On Sep 5, 2008, at 9:33 AM, Jeff Jenkins wrote:
>
>> I am running squid2.5.STABLE10.  When a client specifies a non-FQDN
>> name  ("foo", instead of "foo.goo.com"), squid fails to resolve the
>> name.   The machine squid is running on is configured to use DNS
>> servers that can resolve that name.  I can do nslookups on foo on
>> the squid host machine w/o failures.
>>
>> Is there some config that controls this?
>>
>> Thanks!
>>