You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i run local Unbound resolver for all mail server instances; as is the recommended best-practice for, in my case, Postfix + Unbound on linux.
qname minimization usage is strongly recommended by the main resolver vendors.
otoh, use of Spamhaus (SH) for DNSBL queries recommends DISABLING qname minimization.
e.g., these articles
KB Article: Spamhaus broken with QNAME minimization
https://gitlab.isc.org/isc-projects/bind9/-/issues/4337
QNAME Minimization and Spamhaus
https://kb.isc.org/docs/qname-minimization-and-spamhaus
QNAME Minimization and Spamhaus DNSBLs
https://www.spamhaus.org/resource-hub/dnsbl/qname-minimization-and-spamhaus-dnsbls/
Configuring a DNS resolver for enhanced performance
https://docs.spamhaus.com/datasets/docs/source/40-real-world-usage/Dns/000-intro.html
conflict in that recommended (non-)usage of qname min ...
ISC says SH is broken and wrong in its recommendation, and that
SH says it's working with the community, but there's no current information available.
SH support responds to inquiry saying there's work on the issue, but no ETA yet.
they recommend in the interim to configure a dedicated resolver specifically for MX spam scanning instance, and turn off Qname minimization.
with the caveat that'd disable qname for all queries on the resolver by the MX -- not just to the SH domains.
as a preferred alternative, they suggest using a resolver where it's possible to turn off Qname minimization for specific domains only.
i run local Unbound resolver for all mail server instances; as is the recommended best-practice for, in my case, Postfix + Unbound on linux.
qname minimization usage is strongly recommended by the main resolver vendors.
otoh, use of Spamhaus (SH) for DNSBL queries recommends DISABLING qname minimization.
e.g., these articles
conflict in that recommended (non-)usage of qname min ...
ISC says SH is broken and wrong in its recommendation, and that
SH says it's working with the community, but there's no current information available.
SH support responds to inquiry saying there's work on the issue, but no ETA yet.
they recommend in the interim to configure a dedicated resolver specifically for MX spam scanning instance, and turn off Qname minimization.
with the caveat that'd disable qname for all queries on the resolver by the MX -- not just to the SH domains.
as a preferred alternative, they suggest using a resolver where it's possible to turn off Qname minimization for specific domains only.
at the moment, that's reported as just Knot
whereas for Unbound
it's all-or-nothing.
this is a Feature Request to add similar capability to Unbound -- specifically to add per-domain exclusion for qname minimisation.
The text was updated successfully, but these errors were encountered: