Hi. Whilst I (think I) understand the intent of this modification a slight problem I’m seeing is that my iPhone appears not not to be able to resolve hostnames on my local domain using conditional forwarding. Is this an intentional outcome? Is there a workaround to this?
Pi-hole's resolution of local domains is unrelated to Implement _dns.resolver.arpa as a special domain or add BLOCK_SVCB as a configuration option.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
sudo pihole -d
or if you run your Pi-hole as a Docker container:
docker exec -it <pihole-container-name-or-id> pihole -d
where you substitute <pihole-container-name-or-id> as required.
Hi.
https://tricorder.pi-hole.net/Dji7l9Nx/
Local hostname lookups appear to be working from MacOS device, but not IOS or IPadOS.
Thanks for the help.
How do your iPhone's DNS requests register in Pi-hole's Query Log, in particular when you are trying to access a local domain from your iPhone?
Unrelated to your observation, I noticed some issues in your debug log.
Your Pihole machine (and probably your network) has local IPv6 connectivity only, so Pi-hole can't talk to IPv6 upstream servers.
However, you have configured a number of IPv6 upstreams for your Pi-hole, which would prompt Network unreachable errors whenever Pi-hole tries to forward a DNS request to one of those:
-rw-r----- 1 pihole pihole 98K Aug 16 12:02 /var/log/pihole/FTL.log
-----head of FTL.log------
2025-08-16 00:00:14.995 BST [624M] WARNING: Connection error (2001:4860:4860::8888#53): failed to send UDP request (Network unreachable)
2025-08-16 00:01:48.809 BST [624M] WARNING: Connection error (2001:4860:4860::8888#53): failed to send UDP request (Network unreachable)
You should untick all IPv6 addresses from your Pi-hole's list of Upstream DNS servers.
Pi-hole also logged quite a few failed attempts to call its API, e.g.
2025-08-16 00:04:34.518 BST [624/T2059] WARNING: API: Bad request (key: bad_request, hint: The API is hosted at pi.hole/api, not pi.hole/admin/api)
2025-08-16 00:04:34.521 BST [624/T2059] WARNING: API: Bad request (key: bad_request, hint: The API is hosted at pi.hole/api, not pi.hole/admin/api)
Are you perhaps using some third-party software that hasn't yet been updated to correctly interact with Pi-hole v6?
Your debug log also shows you are running cloudflared's and unbound's DNS resolvers on your Pi-hole machine, though you are using neither of them as Pi-hole's upstream:
*** [ DIAGNOSING ]: Ports in use
udp:127.0.0.1:54 is in use by cloudflared
(…)
udp:127.0.0.1:5335 is in use by unbound
If you don't need them anymore, you could disable or uninstall them.
You also are running two DHCP clients:
udp:0.0.0.0:68 is in use by dhclient
udp:0.0.0.0:68 is in use by dhcpcd
This could prompt race conditions when acquiring a DHCP lease, either resulting in inability to acquire a lease, or in frequent renewals of your machine's DHCP lease.
You should decide on one DHCP client software and disable or uninstall the other.
Thanks. Think I might have upgraded too many times. I’m going to do a piHole rebuild and see what happens.
Hi - built new version of piHole - https://tricorder.pi-hole.net/VaXck9gW/
Weird thing is I’m not seeing any queries identified from the iPhone in the log - even though I can see in the iPhone settings that the DNS IP addressed has been picked up for piHole.
Just realised I’m an idiot. Appears NordVPN’s threat protection was on in the background. Apologies. At least I’ve got a new PiHole instance now…
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.