Search Domain Not Working With Squid

domain-name-systemsquid

I just set up a squid proxy as a parent proxy to HAVP. When I or other users try to access a domain with an address like "http://foo" I get the following squid error in the browser:

The dnsserver returned:

    Server Failure: The name server was unable to process this query.

However, "http://foo.companyname.com" works fine. The search domain in resolv.conf on both the client and proxy host is companyname.com. (There a better term for "search domain"?)

Is there a way to correct this, maybe something in the squid.conf file?.

Best Answer

I needed:

append_domain .mycompany.com

in my squid.conf file. (Thought I grepped through conf for domain, must have missed it the first time).

Related Solutions

Using both domain users and local users for Squid authentication

Now, I need a way to allow access to users which don't have a domain account. Can this be done?

Yes.

How?

You can use an "external" ACL helper, which allows you to roll your own mechanism. See the Squid wiki "Multiple Source" entry for more details. This bit of pseudo-code lifted straight from there:

auth_param basic program /usr/local/bin/my-auth.pl
external_acl_type myAclType %SRC %LOGIN %{Proxy-Authorization} /usr/local/bin/my-acl.pl
acl MyAcl external myAclType
http_access allow MyAcl

... where my-auth.pl is a bit of perl script that performs the actual authentication, and returns OK or ERR as the result.

Squid not resolving a particular URL

Delegation of the zone "www.standardandpoors.com" (note the zone begins www) is broken.

The servers for standardandpoors.com say there are two name servers for www.

These two servers answer for A requests but not for "NS" requests, or other requests - despite claiming to be BIND 9.4.3-P3. They answer for SOA requests for the parent domain.

I assume either some sort of load balancer (I've seen them broken like this before), or just the normal borked nature of many DNS delegations. BIND 9 seems to handle this form of borked delegation adequately.

As others asked - what name servers are not handling this well? Are you messing with forwarding, or slaving zones, or similar internally?

Best Answer

Related Solutions

Using both domain users and local users for Squid authentication

Squid not resolving a particular URL

Related Topic