Issues w/ Latest update

Nice catch!!!! This would have had me on a wild goosechase forever!! There have been no updates to PiHole or CloudFlared and that setup predates my Channels subscription, so I only ensured that PiHole wasn't blocking certain DNS queries, but I never explored CloudFlared!! I'll contact them via Github and inquire about this! Again, thanks for taking a peek at it. New Results below! This is using CloudFlare Public DNS, not the custom CloudFlared DNS.

macbookpro:~ majesty$ traceroute fanc.tmsimg.com
traceroute: Warning: fanc.tmsimg.com has multiple addresses; using 99.84.110.122
traceroute to d1k0gkbv5kl6h3.cloudfront.net (99.84.110.122), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 47.333 ms 2.215 ms 0.830 ms
2 * * *
3 b3335.nwrknj-lcr-21.verizon-gni.net (130.81.27.46) 6.728 ms 7.254 ms
b3335.nwrknj-lcr-22.verizon-gni.net (130.81.27.48) 5.675 ms
4 * * *
5 * * *
6 0.ae10.gw13.iad8.alter.net (140.222.225.219) 10.827 ms
0.ae9.gw13.iad8.alter.net (140.222.225.63) 10.490 ms 11.014 ms
7 amazon-gw.customer.alter.net (204.148.11.46) 10.442 ms 32.530 ms 26.485 ms
8 52.93.40.51 (52.93.40.51) 26.008 ms
52.93.40.55 (52.93.40.55) 34.476 ms
52.93.40.61 (52.93.40.61) 30.656 ms
9 52.93.114.95 (52.93.114.95) 11.921 ms
52.93.114.1 (52.93.114.1) 10.969 ms
52.93.114.81 (52.93.114.81) 9.967 ms
10 * * *
11 * * *
12 52.93.40.243 (52.93.40.243) 14.994 ms 11.495 ms
52.93.40.239 (52.93.40.239) 13.598 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 server-99-84-110-122.iad79.r.cloudfront.net (99.84.110.122) 12.424 ms 10.157 ms 11.589 ms

The Pihole (Local Raspberry Pi) filters all DNS Queries for Ads, Malware, Data Mining, tracking etc. etc. then forwards the allowed queries to a cloudflare upstream server that delivers DNS over HTTPS. In my case 127.0.0.1#5053 Can you PLEASE look into this to see if it's something on the DVR side that can be done so that I can continue to use my current setup? This all worked beautifully together before with no issues. I manually update and manage that server via SSH in a headless setup. I can certainly tell you that other than Pihole admin page updates, nothing concerning cloudflared has changed. @tmm1

That did the trick. All thumbnails were just there when the guide was loaded. Something must have changed w/CloudFlare.

pihole updates gravity every week, by default. Many blocklists include geolocation services.

Yeah, but I checked that yesterday and ruled the PiHole out. No DNS queries coming from Channel's were being touched.

I am running PiHole and haven’t had any of these issues. I’d definitely say CloudFlare is the issue.

1 Like

The problem appears to be specific to how CloudFlare's DoH works. It's breaking geolocation and causing images to be downloaded from Asia, which is ofcourse quite slow. Using PiHole with a regular DNS upstream should fix the issue.

1 Like

Switched to Unbound and the issue went away. What a wild goose chase that was.

Hello @tmm1. Yeah, I switched to Unbound, and the issue is no longer present. Thanks for your time and helping me track this down. There were no changes on my side, but they have most likely made changes to the servers they’re using for some reason. Once I read more on it, I quickly realized there’s nothing you can do. I appreciate the time you guys spent looking into this.

4 Likes

@Macnbaish @EdwinG Thanks guys! Your recommendations were spot on and eventually led to the culprit. I removed CloudFlared and installed Unbound in its place and I'm now seeing <1ms response times on cached queries. 2-3ms responses on cold hits! Thanks for chiming in.

1 Like