Search squid archive

Re: can squid use dns server on random port(non-53)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Date: Thu, 28 Jun 2018 07:06:14 +1200
From: Amos Jeffries <squid3@xxxxxxxxxxxxx>
To: squid-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: can squid use dns server on random
        port(non-53)?
Message-ID: <4563f027-a210-deeb-df82-f5a238887410@xxxxxxxxxxxxx>
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 it
>> 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.
>


Amos


I agree it's a bit unusual, but adding a nameserver port option will be nice if the changes are not intrusive.

Thanks,
Gordon 
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux