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?
Thanks,
Gordon
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo
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?
maybe you can use a dns resolver like unbound, dnscache, dnsmasq,
which can be configure to listen on loc
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 re
Date: Thu, 28 Jun 2018 07:06:14 +1200
> From: Amos Jeffries
> To: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] can squid use dns server on random
> port(non-53)?
> Message-ID: <4563f027-a210-deeb-df82-f5a238887...@treenet.co.nz>
> Content-Type: t
This is actually standard practice, it is very easy and common for
administrators to configure their firewalls to redirect all 53 tcp/udp
requests to a specific host to prevent those people and/or malicious
applications which may be smart enough to change their dns server
settings in an attempt
On 28/06/18 09:16, Gordon Hsiao wrote:>
> I agree it's a bit unusual, but adding a nameserver port option will be
> nice if the changes are not intrusive.
So what protocol is used on this non-53 port?
How does "HTTP" sound? yes DNS-over-X is a thing these days and only
port 53 has the assurance t
On 06/27/2018 03:16 PM, Gordon Hsiao wrote:
> adding a nameserver port option will be nice if the changes are not intrusive.
Agreed. There are legitimate use cases for custom DNS ports. Just
because somebody might misuse a custom DNS port does not mean it should
not be supported (port 53 itself h
