[squid-users] can squid use dns server on random port(non-53)?
capcoding at gmail.com
Wed Jun 27 21:16:43 UTC 2018
Date: Thu, 28 Jun 2018 07:06:14 +1200
> From: Amos Jeffries <squid3 at treenet.co.nz>
> To: squid-users at lists.squid-cache.org
> Subject: Re: [squid-users] can squid use dns server on random
> Message-ID: <4563f027-a210-deeb-df82-f5a238887410 at treenet.co.nz>
> Content-Type: text/plain; charset=utf-8
> On 27/06/18 16:29, Dieter Bloms wrote:
> > Hello,
> > On Tue, Jun 26, Gordon Hsiao wrote:
> >> checked the manual it seems I can only set dnsserver with a new IP, is
> >> possible to make squid support non-standard DNS port, e.g. 5353?
> Squid only contains a minimal stub resolver. It requires a recursive
> resolver on port 53 (UDP *and* TCP) to do the actual DNS resolving and
> any fancy things like strange ports.
> So what Dieter said:
> > maybe you can use a dns resolver like unbound, dnscache, dnsmasq, ....
> > which can be configure to listen on localhost port 53, so only squid can
> > access it via localhost and no other servers.
> > These dns resolvers can be configure to use a non standard port like
> > 5353 for the destination dns servers.
> > But in the past I've never seen a dns server listening on port 5353, so
> > maybe the setup is a little broken.
> I agree it's a bit unusual, but adding a nameserver port option will be
nice if the changes are not intrusive.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users