Sites can't be reached but then it refreshes and is fine

This has been happening with differing frequency over the last few weeks. When visiting some websites, the site will momentarily not load (give a chrome error that the IP is not found), and then immediately refresh and load.
Sample:
image

I read through the logs to the best of my ability but didn't see anything of note. Debug is attached.

The latest example of this behavior was with iod.com. I took the debug log immediately after this behavior occurred. This is going from a google search to clicking google's link to the website.

Expected Behaviour:

Sites load seamlessly and quickly, as they have been for over a year.

Actual Behaviour:

Sites flash with error that IP is not found, and then immediately refresh and load.

Debug Token:

n9qdkwcnqe

If you look in the log (/var/log/pihole.log), do you see any of the queries match up with what you are seeing? If not, it may be a client-side issue.

This is the log segment for a site where I saw the issue. It is happening on multiple computers, not just mine.

Doesn't look weird to me?

Jan 14 01:41:48 dnsmasq[642]: forwarded www.iod.com to 8.8.8.8
Jan 14 01:41:48 dnsmasq[642]: query[A] google.com from 192.168.1.1
Jan 14 01:41:48 dnsmasq[642]: forwarded google.com to 8.8.8.8
Jan 14 01:41:48 dnsmasq[642]: reply google.com is 172.217.6.238
Jan 14 01:41:48 dnsmasq[642]: reply www.iod.com is 78.40.150.80
Jan 14 01:41:48 dnsmasq[642]: query[A] www.iod.com from 192.168.1.1
Jan 14 01:41:48 dnsmasq[642]: cached www.iod.com is 78.40.150.80
Jan 14 01:41:49 dnsmasq[642]: query[A] api.segment.io from 192.168.1.1
Jan 14 01:41:49 dnsmasq[642]: /etc/pihole/gravity.list api.segment.io is 0.0.0.0
Jan 14 01:41:49 dnsmasq[642]: query[A] rum.monitis.com from 192.168.1.1
Jan 14 01:41:49 dnsmasq[642]: /etc/pihole/gravity.list rum.monitis.com is 0.0.0.0
Jan 14 01:41:49 dnsmasq[642]: query[A] cloud.typography.com from 192.168.1.1
Jan 14 01:41:49 dnsmasq[642]: forwarded cloud.typography.com to 8.8.8.8
Jan 14 01:41:49 dnsmasq[642]: reply cloud.typography.com is <CNAME>
Jan 14 01:41:49 dnsmasq[642]: reply wildcard.typography.com.edgekey.net is <CNAME>
Jan 14 01:41:49 dnsmasq[642]: reply e7100.g.akamaiedge.net is 104.70.67.120
Jan 14 01:41:50 dnsmasq[642]: query[A] www.googletagmanager.com from 192.168.1.1
Jan 14 01:41:50 dnsmasq[642]: /etc/pihole/gravity.list www.googletagmanager.com is 0.0.0.0
Jan 14 01:41:52 dnsmasq[642]: query[A] connectivitycheck.gstatic.com from 192.168.1.1
Jan 14 01:41:52 dnsmasq[642]: forwarded connectivitycheck.gstatic.com to 8.8.8.8
Jan 14 01:41:52 dnsmasq[642]: reply connectivitycheck.gstatic.com is 172.217.6.227```

Pi-hole appears to be working fine. It is probably an issue with the browser or Windows.

I dumped all of my hosts information, restarted my router, cleared my cache. Everything. It only resolves when I disable pihole for a while.

Also, his is happening on multiple computers.

Are they all Windows computers?

Yes. As far as I know. I don't think we have had the issue on any other devices.

Since the issue is only happening on Windows computers, try contacting Windows support or seeing if it's a known issue there.

Yeah, I think I see the issue now. Sorry for posting this here.

When I point my DNS on my PC directly to the Pihole, it works fine. I'll see if my husband is still having this issue on his PC.

Thank you for your help :slight_smile:

What did you find to be the problem? Was it a Windows setting or something in the router settings?

I didn't find the exact problem, other than that it could be a router setting. When I set the DNS entry directly to the pihole in my local network settings on the windows PC, it seems to resolve the problem.

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.