I'm experiencing periodic 'page not found' errors when browsing. I cannot figure why this happens, there appears to be no pattern, just seems random
If I refresh (F5) the page, it will sometimes appear. It may take a couple of refreshes. If I select 'Restart the DNS resolver', the page will usually load. If not, and the page will not F5 refresh after numerous attempts, then I have to reboot both DNS and modem.
If I look at the query log, the domain is returned as status OK. Nothing appears wrong from looking at the logs.
For info, I previously raised this here...
If it's not a pi-hole problem, any suggestions as to how to track this down and fix it. It's darned frustrating!
Your debug log is normal. Check in the dnsmasq log at /var/log/pihole.log and see if there are significant delays between the query for a domain and the received reply for the same domain.
Thanks for the assistance. I've just had a 'page not found' now. The dnsmasq log shows...
Oct 28 09:32:30 dnsmasq[16153]: query[A] dr-chatard-jean-michel.chirurgiens-dentistes.fr from 192.168.1.30
Oct 28 09:32:30 dnsmasq[16153]: forwarded dr-chatard-jean-michel.chirurgiens-dentistes.fr to 127.0.0.1
Oct 28 09:32:31 dnsmasq[16153]: reply dr-chatard-jean-michel.chirurgiens-dentistes.fr is 213.186.33.16
Your log excerpt shows that Pi-hole has done its part and correctly has handled and answered that request by providing the respective IP address.
ERR_ADDRESS_UNREACHABLE would suggest a networking issue, i.e. your client knows no way to contact that IP address. This may either be a temporary (e.g. because a wifi connection was disrupted) or consistent failure (e.g. because a firewall is blocking access to that specific IP).
Run from the client that is triggering the page not found message, and preferably right when that message occurs, what is the result of:
ping 213.186.33.16
(The IP address is - of course - specific for the domain that cannot be accessed).
Now I am baffled. That consistently returns (on ctrl-c) a 100% packet loss. As does a ping of the url. However, the page loads in both the browser I normally use (presumably from cache??) and from a different browser.
Not sure if it helps but traceroute on that same ip stops after 8 jumps....
traceroute to 213.186.33.16 (213.186.33.16), 30 hops max, 60 byte packets
1 4g-modem (192.168.1.1) 0.381 ms 0.308 ms 0.260 ms
2 192.168.0.1 (192.168.0.1) 3.286 ms 3.320 ms 3.248 ms
3 10.64.28.94 (10.64.28.94) 34.466 ms 34.397 ms 41.154 ms
4 10.64.67.62 (10.64.67.62) 40.990 ms 40.839 ms 40.771 ms
5 10.64.67.57 (10.64.67.57) 40.716 ms 41.830 ms 41.678 ms
6 ei-telecom-gw1.ter4.eqx2.par.cust.as8218.eu (83.167.60.229) 40.437 ms 37.026 ms 38.040 ms
7 ae12.ter4.eqx2.par.core.as8218.eu (83.167.60.228) 90.854 ms 95.289 ms 95.180 ms
8 ae6.ter3.eqx2.par.core.as8218.eu (83.167.55.42) 40.401 ms 35.463 ms 35.341 ms
9 * * *
10 * * *
I reckon I've got some kind of network problem. It's got me flummoxed, over and above my knoweldge.
Yes, thanks. I've been doing a bit of reading since (just to try and understand) and it seems that ping requests can be blocked.
I wish I knew what was going on. As I mentioned in my other post, I'm behind CGNAT and I don't know whether that will inherently lead to more chance of time out.