Sites and Apps should be loading under iOS with a pi.hole DNS. But in 30% of the time sites and apps didn't load, so I have to turn off w-lan and surf with mobile data. We have all the problems and guests too. With my Windows 10 PC and android anything is fine.
##My Setup
I use pi.hole 5 with a raspbarry pi 3. All devices are using the pi.hole DNS, the DNS get spread by my fritz.box. To find a solution I entered the pi.hole DNS hard into my iPhone/iPad and don't set it to automaticaly.
Your debug log is normal. Let's take a look at the DNS servers that your IOS device is using. On the IOS device, settings > wifi > select the circle i next to the active wifi connection > DNS > Configure DNS. What DNS servers are shown (a screen capture will be helpful). Here is an example of an IOS device configured to use two Pi-holes:
Tail the pihole log (from either the web admin GUI or the terminal with pihole -t) and load some apps and websites on the IOS device. Do you see the expected DNS traffic? Are any domains not being resolved?
Hi jfb, I can see everything. Sometimes if sites did not load I switch to mobile data. Than anything works. After one minute in wlan the same site before works with pi.hole too.
This might be explained by browser caching. While on mobile data domains are loaded and DNS data ist stored in the browser cache. After switching to wifi the browser still uses the data from the cache instead of requesting a new DNS resolution.
Your problem sounds like overblocking. How many domains do you have on your adlists?
You could open an app / webpage that you know isn't working and look in your query log what is blocked and selectively whitelist the needed domains.
Hi and thanks. I just use the standard adlist. I don't add addtional lists. The sites are often diffrent. For example my own blog didn't load sometimes, but my site have no tracking. And sometimes im in the w-lan and anything works fine, but after thirty minutes sites didn't load.
In theory it should not matter - but in real life ethernet is more stable and often less buggy than wifi. Wifi introduces more possible points of failure than a plain copper cable. If you have the ability to change it - try it as well.
