Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Identify what the resolver supplied
RFC 6147 describes DNS64 synthesis of AAAA records from A records, used with a translator to let an IPv6 only client communicate with an IPv4 only server for applicable applications. Therefore an IPv6 shaped answer observed on such a network does not alone establish that the origin server publishes a native IPv6 endpoint. The resolver and translation context are part of the evidence, rather than an incidental detail which can be discarded.
Compare the source of two answers
For an original diagnostic plan, record the exact hostname and record type, then note whether the network documents DNS64 service. If comparing answers from another environment, keep the resolver context alongside each result. Different answers may reflect synthesis rather than a recent server migration. Do not replace the network resolver casually when its documented translation design depends on that resolver behaviour. A manual public resolver substitution can change the conditions being tested.
Keep conclusions appropriately narrow
A successful connection through translation demonstrates that tested path, not universal native IPv6 support or identical behaviour for every application. Conversely, one failing app does not invalidate every translated connection on the network. Preserve the actual request and failure stage when escalating to its maintainer. This article explains a DNS and network translation boundary; it does not identify UK IPTV infrastructure, recommend bypassing access controls or promise compatibility for all literal address and application designs.