Keep the query type with the answer
A lookup for IPv4 and a lookup for IPv6 ask different questions. Preserve the actual query type, resolver, time and answer. Do not reduce every empty result to NXDOMAIN, which has its own missing-name meaning.
An application can choose among available addresses according to its implementation and network conditions. A working browser and failing player may not select the same family or destination. Label the application and device difference rather than assuming identical paths.
Separate publication from reachability
An address being published does not prove a working route to it from every network. Conversely, a reachable IPv4 service does not establish that its IPv6 counterpart is correctly configured. The operator may need to inspect both publication and service reachability.
An illustrative hostname can publish both families while one route fails. That is a dual-stack investigation, not proof that the entire domain or subscription is unavailable. A 403 received after connection is a different result from failure to resolve or connect.
Use a supported family comparison
Have the network administrator or provider test the same intended destination over the supported families where appropriate. Keep the resource, account and time comparable. Record the first failed stage rather than simply marking IPv6 good or bad.
Do not permanently disable a family throughout the household based on one unexplained sample. Preserve original settings and the intended network design. Some provider arrangements depend on their configured IPv6 and translation mechanisms.
Report safe naming evidence
The hostname and answer type usually suffice for an initial DNS report. Full media paths, cookies and token values are unnecessary and should remain private. If a numeric address is requested for a legitimate diagnostic, share it through an appropriate route with its observation time.
After a documented correction, retest the original player and programme. A successful lookup is only one stage; secure identity, account permission and media delivery remain separate. The useful conclusion identifies which family and request stage were actually verified without turning a DNS record into a performance guarantee.
Related questions
Does an AAAA record mean every household device uses IPv6 for that service?
No. Client capability, network configuration and address selection affect the actual connection.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- RFC 3596 — Relevant protocol definition only; household workflows and numerical examples are editorial.
- RFC 8200: Internet Protocol, Version 6 — IPv6 addressing and packet-delivery design; troubleshooting scenarios are editorial.
