[sokoloff]

Oh no, I was trying different bits of routing trickery. I'm pretty sure if I sat down and gave it a solid 3 hours straight of methodical effort, that I'd have figured it out once and for all. Instead, I would have 5-10 minutes total per attempt, try something, see if it worked or didn't, then the next time I tried the Chromecast (possibly weeks later), it wouldn't always be repeatable. I also had the Casts being powered off the TV, so they got hard shutdown and cold-booted pretty often.

In short, I never really cared enough to get it working right as the FireTV was "winning" the convenience battle by enough to make it not matter most of the time and I always had an HDMI cable for the times when I really had to get a screen "sharing" to work.

[Dah00n]

Did you block Google's DNS IPs? That will break Chromecast in strange ways.

[KeepFlying]

Maybe someday I'll write a rewrite rule to pass google DNS through my PiHole...maybe.

All of this hardcoded DNS server BS in iot devices is a pain.

[Dah00n]

A warning from someone who did exactly this:

https://news.ycombinator.com/item?id=27214320

TL;DR I tried to force Chromecast (and everything else) to use Pihole as DNS and misbehaving devices (like Chromecast) hammered my pihole into oblivion. I'm talking tens of thousands of requests in a very short amount of time which caused my RPI4 to stop responding to DNS requests (dashboard was still working though). See linked comment thread for details but suffice to say 4 virtual machines with pihole behind two load balancers still saw some downtime. OPNsense gateway is a much better (and safer!) fix IMO :)