hosts file is identical on both systems
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 raspberrypi.localdomain raspberrypi
# pdns-recursor
127.10.10.9 pdns-recursor-IPv4
# unbound
127.10.10.2 unbound-IPv4
v5 - correct
v6 - missing
1 Like
DL6ER
November 13, 2023, 9:19am
2
Thanks for the report! Will be fixed by
pi-hole:development-v6 ← pi-hole:fix/upstream_names
opened 09:19AM - 13 Nov 23 UTC
# What does this implement/fix?
Before:
After:
**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.
1 Like
after the latest update, the issue is only partially solved
Pi-hole version is development-v6 v5.17.1-217-gaf9b8df1 (Latest: v5.17.2)
jfb
November 14, 2023, 2:19pm
4
What device on your network is able to resolve the domain name that matches IP 127.10.10.9?
1 Like
