Hi all,
I’m opening this topic as a follow-up to this closed GitHub issue:
https://github.com/pi-hole/FTL/issues/1487
The issue was closed prematurely despite presenting a critical bug:
When a conditional domain is matched even once, all future queries are silently forwarded to that conditional’s upstream, bypassing the default DNS. The query log continues to falsely report that the default DNS is in use, making this failure very hard to detect.
This happens even with a single conditional domain and a single upstream. Once matched, it silently takes over all future DNS queries. It is reproducible, tested with Pi-hole Nightly, and includes verbose logs and diagnostics in the original GitHub thread.
The GitHub issue was dismissed without addressing the core problem, with the rationale that the author used an LLM for wording and that maintainers are volunteers—neither of which are valid grounds to ignore a clearly demonstrated bug.
I personally invested days diagnosing this and even set up Nightly versions per the maintainer’s request. I was never informed that the config system had changed and that dnsmasq.d was no longer applied unless manually enabled. I had to discover this myself after wasting hours debugging why nothing was taking effect. I also identified the specific behavioral shift in query routing and logging—none of this was acknowledged.
This is a serious security and integrity issue that misrepresents what DNS servers are actually used while breaking expected routing behavior. It deserves a full review, not a dismissal based on process.
Please review the original report and reopen the issue, or provide a formal explanation for the intended behavior. The bug, as documented, is easy to replicate and severe in scope.
Thanks.