set interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 interface eth1 no-dns

or equivalent for your setup, this will prevent ISP ipv6 DNS servers from being assigned to clients 

I'm having problems with Chromecast on the network. I have a pretty vanilla setup as per the guide other than DNS redirection for a couple of TVs.

Any ideas?

Edit: I've done a substitution test with another router (Linksys E1200 and it's definitely the edgerouter setup causing the problems. As soon as I drop in the Linksys everything works fine

You don't even define what the "problem" actually is.

Chromecast doesn't work

The edge router doesn't have wifi....

There is zero issues with the Edgerouter and Chromecast

The Nvidia Shield TV has built in Chromecast and that works fine with my ER4. Only suggestion is to reset to factory and start with the default configuration you get with the wizard

My edgerouter lite works great with my chromecast and always has.

@Handle9 The Chromecast should just work unless if you're operating the Edgerouter in bridged mode (which also disables offloading). I've got an Edgerouter X set up at my parents with 2x access points running off it and have no problems with the Chromecasts. If you're operating another Edgerouter (eg the Edgerouter 4 or Lite) with bridging then I can imagine this will cause issues.

Use a switch, don't use the Edgerouter for switching unless if it is the Edgerouter X or Edgerouter PoE. If you're already doing that then it can't possibly be the Edgerouter causing the issue here - you need to provide more information.

With the DNS NAT redirection you're doing have you also blocked Google DNS? Blocking it might break chromecast, you'd need to redirect it as well

The network architecture is as below:

Casting doesn't work.

When I substitute a vanilla TP-Link as below (with the Pihole as DNS server) it does allow casting. 

@michaelmurfy this draws me to the conclusion that something in the Edgerouter Lite 3 setup is causing the problems. The Edgerouter connects to the ONT via PPPoE on eth0. The Edgerouter connects to the switch on eth1.

I have also tried:

ISP DNS servers instead of Pihole and disable all DNS redirection

dfnt:

set interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 interface eth1 no-dns

or equivalent for your setup, this will prevent ISP ipv6 DNS servers from being assigned to clients 

iamsammajor:

dfnt:

 

set interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 interface eth1 no-dns

 

 

 

or equivalent for your setup, this will prevent ISP ipv6 DNS servers from being assigned to clients 

 

Could you tell me more about the reason on this?

I don't know if its EdgeRouter specific as IPV6 is overly complicated enough as it is, that I can't be bothered researching all the details myself. However, with dhcpv6-pd + SLAAC configured on the EdgeRouter it sends the ISP's DNS servers, in addition to other IPV6 details, to clients.

If you use pihole, for example, or your own DNS server then you don't want the ISP's DNS servers presented to clients because they will favour IPV6 over IPV4

This becomes an issue if you use pihole to block ads, as the client will prefer the IPV6 address of the ISP's DNS server ads will show if they're served over IPV6

The above config doesn't prevent the EdgeRouter from obtaining the ISP's IPV6 DNS server addresses, it just prevents slaac from sending it to the clients

dfnt:

 

iamsammajor:

dfnt:

 

set interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 interface eth1 no-dns

 

 

 

or equivalent for your setup, this will prevent ISP ipv6 DNS servers from being assigned to clients 

 

Could you tell me more about the reason on this?

 

I don't know if its EdgeRouter specific as IPV6 is overly complicated enough as it is, that I can't be bothered researching all the details myself. However, with dhcpv6-pd + SLAAC configured on the EdgeRouter it sends the ISP's DNS servers, in addition to other IPV6 details, to clients.

 

If you use pihole, for example, or your own DNS server then you don't want the ISP's DNS servers presented to clients because they will favour IPV6 over IPV4

 

This becomes an issue if you use pihole to block ads, as the client will prefer the IPV6 address of the ISP's DNS server ads will show if they're served over IPV6

 

The above config doesn't prevent the EdgeRouter from obtaining the ISP's IPV6 DNS server addresses, it just prevents slaac from sending it to the clients

 

i thought pi-hole does work that good anymore since google has a way to merge the AD into the video, maybe i am wrong.

anyway thanks for the info :)

Of the 23k DNS requests today 5k have been blocked, or 20% so it still has its uses other than just youtube

Yes more services are getting smart about serving ads from the same domain as the video rendering DNS blocking useless for them, but I never used it for that purpose anyway and I still use ublock origin in browsers