Mobile app should be able to communicate with server through any protocol or connection type when pihole is enabled/disabled.
Actual Behaviour:
Using iPhone and iPad, some mobile app no longer function properly when pihole is used as DNS.
Even if i disable pihole, those same mobile apps do not work correctly.
If i set the router's DNS or other public DNS manually, the app works correctly.
The major problem is with Brawl Stars game, where the game authenticates correctly, says it's connected to the server, BUT when you actually start a match with other players, it fails to find network connection.
Even if i disable pihole form webui, same thing happens.
If i switch to mobile connection after connection failed from pihole, it connects succesfully.
If i start match from mobile connection, then connect to wifi+pihole, it fails to connect.
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.1.199/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
*** [ DIAGNOSING ]: Setup variables
...
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.16/24
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
...
[✗] Failed to resolve go.dice.fm via Pi-hole (192.168.1.16)
And multiple active interfaces? Your DHCP server is not passing the IP of Pi-hole for DNS, either.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 300 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.199
Server IP address: 192.168.1.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86399 ( 23h 59m 59s )
--- end of options ---
* Received 300 bytes from wlan0:192.168.1.1
DHCPOFFER hardware address did not match our own - ignoring packet (not for us)
DHCPREQUEST chaddr: b8:27:eb:fc:85:6f (our MAC address)
DHCPOFFER chaddr: b8:27:eb:a9:d0:3a (response MAC address)
* Received 300 bytes from eth0:192.168.1.1
DHCPOFFER hardware address did not match our own - ignoring packet (not for us)
DHCPREQUEST chaddr: b8:27:eb:a9:d0:3a (our MAC address)
DHCPOFFER chaddr: b8:27:eb:fc:85:6f (response MAC address)
* Received 300 bytes from wlan0:192.168.1.1
Offered IP address: 192.168.1.198
Server IP address: 192.168.1.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86399 ( 23h 59m 59s )
--- end of options ---
DHCP packets received on interface lo: 0
DHCP packets received on interface eth0: 1
DHCP packets received on interface wlan0: 1
Indeed I configured it first on wlan, then moved it to eth0 that has 192.168.1.199.
I updated /etc/pihole/setupVars.con but im still getting the same behaviour after restarting pihole.
I've disabled pi-hole on my network, and used the default settings.
I'm still experiencing the same problem.
I think this is not related to pi-hole, but it might be related to my router config, im using a mikrotik router.
Ill look for help with the miktrotik community.
Once you fix the issue on the routers end, I'd recommend you re-install PiHole to make sure you start with a clean slate and avoid any weird issues popping up in the future.
That's just me though, I also started with my PiHole on wlan and then swapped it to eth0 and a clean install definitely helped in my case. (I had issues running it on wlan)