We have a DNS guru on staff and editing the resolv.conf in this manner
does not work (we tested it to make sure). Looks like we are using an
older desktop to setup a basic DNS server and then point squid to redirect.
Mike
On 7/2/2015 2:06 AM, Stuart Henderson wrote:
On 2015-07-01, Mike <mcsnv96@xxxxxxx> wrote:
This is a proxy server, not a DNS server, and does not connect to a DNS
server that we have any control over... The primary/secondary DNS is
handled through the primary host (Cox) for all of our servers so we do
not want to alter it for all several hundred servers, just these 4
(maybe 6).
I was originally thinking of modifying the resolv.conf but again that is
internal DNS used by the server itself. The users will have their own
DNS settings causing it to either ignore our settings, or right back to
the "Website cannot be displayed" errors due to the DNS loop.
resolv.conf would work, or you can use dns_nameservers in squid.conf and
point just squid (if you want) to a private resolver configured to hand
out the forcesafesearch address.
When a proxy is used, the client defers name resolution to the proxy, you
don't need to change DNS on client machines to do this.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
