Daniel-Constantin Mierla writes:
> The DNS NAPTR is also turned off by default, which should be on, based
> on RFC, iirc, but that adds extra DNS query and slows down everything as
> most of services I saw so far do no relay on NAPTR.
It is OK to have NAPTR lookup off by default, but if it is tur
What is the point of dns_naptr_ignore_rfc default value:
dns_naptr_ignore_rfc
If the DNS lookup should ignore the remote side's protocol preferences,
as indicated by the Order field in the NAPTR records and mandated by RFC
2915.
dns_naptr_ignore_rfc = yes | no (default yes)
In my (and RFC 291
On 10.08.20 17:08, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> The DNS NAPTR is also turned off by default, which should be on, based
>> on RFC, iirc, but that adds extra DNS query and slows down everything as
>> most of services I saw so far do no relay on NAPTR.
> It is OK to ha
I have not developed that feature, but many options are not following
the recommendations from RFCs with their default values, but more what
was the common practice/best supported at that time (e.g., auto-switch
protocol to tcp/tls on mtu size).
The DNS NAPTR is also turned off by default, which s
