The module asked every upstream with DNSSEC OK and handed the upstream's
additional section back untouched, so a client got an OPT record it never
sent — carrying the module's loop token and the DO flag — and RRSIG
records it did not ask for. macOS's resolver treats such an answer as
invalid and waits out its 30-second timeout on every uncached name, which
made the tun mode's loopback resolver unusable there. Upstream queries no
longer set DO (the module validates nothing), and the response is
rewritten to the client's EDNS: no OPT when the client sent none, a fresh
OPT with the client's UDP size and DO bit when it did, and RRSIGs only for
a DO client.
A rule that sends a name to a local resolver which forwards back to v2rayA
makes the two exchange the same query until one of them runs out of memory;
v2rayA/v2rayA discussion #1950 reproduces it with dnsmasq on OpenWrt. The
firewall-level self-redirect is already handled by the 0x80 mark, but nothing
saw the loop at the resolver level.
Every query this process sends upstream carries a random per-process token in
an EDNS0 local option. A query that arrives carrying that token has come back
around such a loop and is answered with SERVFAIL, with one log line per ten
seconds naming the question and how many were refused.