DNS over HTTPS encrypts DNS queries between a compatible client and resolver. It does not encrypt all traffic from the device and does not replace HTTPS on the media connection. Whether a particular player uses it depends on its implementation.
Separate the traffic types
A browser's secure-DNS setting may apply to browser requests without affecting a television app. Operating-system and router settings can differ again. Avoid assuming that one setting covers every application on the home network.
Check managed-network behaviour
Custom encrypted DNS can conflict with a network's intended filtering or internal names. On an office or school connection, ask the administrator instead of overriding policy. At home, record the original configuration before testing a documented resolver.
Judge the actual symptom
Encrypted DNS may address a resolver-privacy concern, but it does not fix a decoder fault or a consistently undersized connection. Keep performance claims narrow and compare the same lookup or connection problem before and after the change.
