Youtube restrict not enforced on TV

Same for me. Youtube app on android tv is not affected by nextdns settings.

I have checked dns settings on tv and they point at nextdns servers. 

Nextdns parental settings added youtube and also checked all other alternativs. 

Please if someone can advice what to do.

The device or the application can bypass your DNS settings if they use direct connection and don't ask for DNS answer. I see it increasing in use.  NextDNS can't block something that it doesn't see. 

One solution is to use AdGuard on the TV or router. 

Hi,

I also saw this behavior on Android devices recently. In details:

Android tries to connect via DNS-over-TLS to the DNS server configured via DHCP (so using port 853 instead of 53).
A home router generally does not respond to this, therefor the device fails back to classic DNS (port 53).

However, I observe the NextDNS servers are replying to DoT request on port 853 but 
they do not use the profile configuration in that case.

So, parental controls and other filtering are not working in such cases.
That's really annoying and I had a hard time figuring out what was going on.

DoT is handled on specific servers (<ID>.dns.nextdns.io), same for DoH (dns.nextdns.io).
However, the servers defined for classic DNS (port 53) still respond to DoT on port 853....

Ideal solutions (from NextDNS):

1- (Best) NextDNS servers could apply the profile configurations on DoT (port 853) request sent on servers  IPs (IPv4 & IPv6) defined via DHCP from the router,  fike for regular DNS (port 53)

2- For the same server IPs, NextDNS servers should not resolve DoT queries on port 853

Alternative solutions from your side:

1- Setup firewall rule to drop request on port 853 except the IPs you defined.
2- Define NextDNS servers' IP on the router itself for it's own use and DHCP to broadcast the router's IP instead of NextDNS one's
3- Manually define DoH or DoT on each device (not always possible... AndroidTVs... MetaQuest... )

Those alternative are not ideal and if your router/FW does not support it or don't know how to do it, you will be left with solution 3...

I really hope NextDNS will find a way to correctly handle those cases.

Bests,

Olivier