Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Inspect the resolver actually in use
A laptop connected to both a wired network and another configured link can have more DNS context than one global server address. The systemd resolvectl manual documents status as showing global and per link settings. Its query output can also identify the protocol and interface associated with a lookup. This is useful when a name resolves on the laptop differently from another viewing device and the first explanation offered is simply that both use the same router.
Keep the comparison narrow
For an original diagnostic exercise, record the status output relevant to the active links, then query the same ordinary public hostname on each device through its normal resolver. Keep the full hostname and observation time. A difference in results should prompt a review of resolver selection and context before changing unrelated media settings. Do not put a private playlist address, password or signed media token into a public support post to demonstrate the issue.
Avoid premature cache clearing
The tool also contains commands which change settings or flush caches, but an initial status inspection need not use them. Save the relevant evidence before taking a corrective action so the original condition remains describable. This procedure applies where systemd-resolved is actually used; the presence of Linux alone does not guarantee that resolver architecture. A successful DNS result establishes name resolution in that context, not successful account authentication, media decoding or programme availability.