Cloaking rules recursing and eventually making the server unusable

[StevePER]

If a cloaking rule matches itself due to the wildcard matching behaviour, dnscrypt-proxy seems to get stuck in a loop and eventually becomes unusable.

This line is in example-cloaking-rules.txt:

yandex.ru                familysearch.yandex.ru       # inline comments are allowed after a pound sign

Any query for a yandex.ru domain matches this cloaking rule and redirects to familysearch.yandex.ru. But dnscrypt-proxy then appears to check familysearch.yandex.ru against the cloaking rules, matches this rule again, and recurses. If I turn query logging on I get log output like this:

[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15467ms	-
[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15468ms	-
[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15468ms	-
[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15466ms	-
[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15469ms	-
[2026-05-02 07:48:03]	127.0.0.1	familysearch.yandex.ru	A	CLOAK	15468ms	-

The server is then unusable for any other queries until it is restarted.

This seems like a bug to me unless there is something else in my configuration that might be causing it.

[jedisct1]

Yes, it should obviously be =yandex.ru.

The example has been fixed, thanks!

[StevePER]

Thanks for the prompt fix!