Keep transport and answer meaning separate
NXDOMAIN, an address answer and a timeout describe different outcomes. TCP or UDP identifies transport context, not whether the name is legitimate or the requested programme is authorized. Record both the observed result and the method where known.
A player may hide DNS details behind a general connection error. Do not claim TCP DNS failed merely because a loading circle appeared. The network administrator or resolver's supported diagnostics should establish the actual boundary.
Understand why response size can matter
A DNS response can require handling beyond a simple small UDP exchange, including retry over TCP in applicable circumstances. Network policy that permits only part of the required behaviour can therefore produce selective problems rather than every name failing identically.
An illustrative ordinary name can resolve while another response path fails under an incomplete policy. That is a transport-policy question to verify. It does not prove the second domain was deliberately blocked, unpublished or associated with an expired account.
Use the network owner's documentation
If DNS transport is suspected, have the administrator follow the resolver and firewall guidance for the actual configuration. Do not open arbitrary inbound ranges, disable the firewall or assume every encrypted-DNS application uses the same settings as traditional DNS.
Keep the hostname and query type identical in a controlled comparison. Changing resolver, name and device together creates a different experiment. Preserve original settings and restore the intended policy after a legitimate diagnostic.
Verify resolution before returning to media
After a supported correction, confirm the relevant lookup and ordinary external access, then the original player action. If an HTTP permission response remains, report it separately. A repaired DNS path does not grant programme entitlement.
Provide safe hostname, time, resolver context and actual error through the established support route. Full media URLs usually add credentials without improving a DNS report. The useful result is a complete supported resolution path, with transport, DNS answer semantics and account authorization each described accurately rather than compressed into “DNS works” from one small sample.
Related questions
Does DNS over TCP mean the programme video also uses TCP?
Not necessarily. Name resolution and media delivery are separate exchanges and can use different protocols.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
