Pi-Hole/dnsmasq
1
0
Fork 0
mirror of https://github.com/pi-hole/dnsmasq.git synced 2025-12-19 10:18:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Documentation for --do-0x20-encode.

Browse Source
This commit is contained in:
Simon Kelley
2025-03-09 16:15:16 +00:00
parent e427d4b0e6
commit fc9135ca9f
2 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CHANGELOG
View File

@@ -113,9 +113,11 @@ version 2.91
badly with rare broken DNS servers which don't preserve the case badly with rare broken DNS servers which don't preserve the case
of the query in their reply. The first time a reply is returned of the query in their reply. The first time a reply is returned
which matches the query in all respects except case, a warning which matches the query in all respects except case, a warning
will be logged. If this coincides with DNS not functioning, it will be logged. In this release, 0x020-encoding is default-off
is necessary to disable bit 0x20 encoding with --no-0x20-encode. and must be explicitly enabled with --do-0x20-encoding. In future
releases it may default on. You can avoid a future release
changing the behaviour of an installation with --no-x20-encode.
Fix a long-standing problem when two queries which are identical Fix a long-standing problem when two queries which are identical
in every repect _except_ case, get combined by dnsmasq. If in every repect _except_ case, get combined by dnsmasq. If
dnsmasq gets eg, two queries for example.com and Example.com dnsmasq gets eg, two queries for example.com and Example.com

10
man/dnsmasq.8
View File

@@ -852,13 +852,17 @@ name on successive queries, for load-balancing. This turns off that
behaviour, so that the records are always returned in the order behaviour, so that the records are always returned in the order
that they are received from upstream. that they are received from upstream.
.TP .TP
.B --no-0x20-encode .B --do-0x20-encode, --no-0x20-encode
By default, dnsmasq scrambles the case of letters in DNS queries it sends upstream as a security feature. Dnsmasq can scramble the case of letters in DNS queries it sends upstream as a security feature.
This technique can interact badly with rare broken DNS servers which don't preserve the case This technique can interact badly with rare broken DNS servers which don't preserve the case
of the query in their reply. The first time a reply is returned of the query in their reply. The first time a reply is returned
which matches the query in all respects except case, a warning which matches the query in all respects except case, a warning
will be logged. If this coincides with DNS not functioning, it will be logged. If this coincides with DNS not functioning, it
is necessary to disable this scrambling with --no-0x20-encode. is necessary to disable the feature. As at version 2.91, 0x20 encoding
is disabled by default, and must be enabled with --do-0x20-encode. The default
may change in the future, so to be sure of its status after an upgrade, set --do-0x20-encode
or --no-0x20-encode in your config. --no-0x20-encode overrides --do-x20-encode or a future default
0x20-encode enable.
.TP .TP
.B --use-stale-cache[=<max TTL excess in s>] .B --use-stale-cache[=<max TTL excess in s>]
When set, if a DNS name exists in the cache, but its time-to-live has expired, dnsmasq will return the data anyway. (It attempts to refresh the When set, if a DNS name exists in the cache, but its time-to-live has expired, dnsmasq will return the data anyway. (It attempts to refresh the