# I can't connect to the internet through Pihole (Android - Wi-Fi)

**URL:** <https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231>\
**Category:** docker\
**Created:** [December 27, 2025, 10:08pm UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231 "2025-12-27T22:08:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xJulian](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/x/a8b319/32.png) [@xJulian](https://discourse.pi-hole.net/u/xJulian)\
**Post date:** [December 27, 2025, 10:08pm UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231/1 "2025-12-27T22:08:10Z")

</div>

Hi, I hope this is the right category.

First of all, I'm new to this. I have a superficial understanding and I've followed tutorials to install Pi-hole using Docker and combined it with Wireguard. Everything seems to work.

I can connect my phone to Pi-hole through Wireguard just fine, but I can't connect to Pi-hole without Wireguard over the same Wi-Fi network.

I've already added Pi-hole's DNS to my phone's network and I have a static IP address for that network, but every time I try to connect, the web interface shows this:

dnsmasq warning: Ignoring query from non-local network (and my phone's IP address)

From what I've read, Pi-hole prioritizes wired connections. However, I discovered through the web interface that I can connect if I enable "Permit all origins" in the DNS settings. But I'm worried because it says it's dangerous to have it set up this way.

I know I can add the DNS to the router, but I don't want to have Pi-hole on the entire network, only on a few selected Wi-Fi devices.

Is there a way to assign static IPs to a sort of whitelist?

I'm using a Raspberry Pi 5 and I have the latest version of Pi-hole, if that's relevant.

I'm a beginner, so if anyone can give me detailed steps, I'd appreciate it. If you need more information, I can provide it, as long as you specify what you need.

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [December 27, 2025, 10:10pm UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231/2 "2025-12-27T22:10:02Z")

</div>

> [@xJulian](#):
>
> and combined it with Wayguard.

Did you mean Wireguard?

---

<div class="post-metadata">

**Author:** ![xJulian](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/x/a8b319/32.png) [@xJulian](https://discourse.pi-hole.net/u/xJulian)\
**Post date:** [December 27, 2025, 10:26pm UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231/3 "2025-12-27T22:26:16Z")

</div>

\*Facepalm

Yes, Wireguard, well now you know how much of a novice I am, haha.

I edited it so that it is better understood

---

<div class="post-metadata">

**Author:** ![DaveOps](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/fbc32d/32.png) [@DaveOps](https://discourse.pi-hole.net/u/DaveOps)\
**Post date:** [October 10, 2026, 10:55pm UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231/4 "2026-10-10T22:55:19Z")

</div>

So what resloved it.

I'm having the same issue.

---

<div class="post-metadata">

**Author:** ![rachelwilson](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/8edcca/32.png) [@rachelwilson](https://discourse.pi-hole.net/u/rachelwilson)\
**Post date:** [October 11, 2026, 10:18am UTC](https://discourse.pi-hole.net/t/i-cant-connect-to-the-internet-through-pihole-android-wi-fi/84231/5 "2026-10-11T10:18:11Z")

</div>

that dnsmasq line about ignoring queries from non-local network is the giveaway. your phone on wifi is reaching pihole from a different subnet, so pihole treats it as non-local and drops it. go to Settings \> DNS and switch interface listening behavior to "Permit all origins", then retry from the phone. the wired machine worked because it was already on the local subnet.
