DL6ER
June 9, 2025, 5:11am
23
At least not between v6.0 and v6.1, see the only change concerning dnsmasq config generation here . Actually, the last relevant change is > 1 year ago and was already part of Pi-hole v6.0:
development-v6 ā fix/domainNeeded
opened 06:56PM - 07 Mar 24 UTC
# What does this implement/fix?
This PR adds two related commits:
- We shoā¦ uld only set `local=/<domain>/` if there is no conditional forwarding setting (v6 supports multiple reverse lookup servers), otherwise, this creates a harmless but nonetheless needlessly confusing configuration (ad46a1018a27b17e1320998743f08b90287e8059)
- If dns.domainNeeded is set, refuse to send plain domain queries (like `laptop`) upstream at all. (231a9853bdca5e4dfdbcde40ea17ec3cdcb7ec46)
**Related issue or feature (if applicable):** N/A
**Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A
---
**By submitting this pull request, I confirm the following:**
1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
## Checklist:
- [x] The code change is tested and works locally.
- [x] I based my code and PRs against the repositories `developmental` branch.
- [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions
- [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
- [x] I have read the above and my PR is ready for review.
When you specify a domain here, your Pi-hole generates a self-consistent configuration, taking into account everything it knows from pihole.toml (incl. conditional forwarding) but not from possibly existing external configuration (as you asked Pi-hole to manage this domain). If you do not want this local=// magic to happen, set dns.domain = "" (an empty string) to have Pi-hole stay away from assuming any configuration for you.
Have you tried this?