Keep the query and connection distinct
A DNS answer lists naming information available through that resolver at that time. The client can then select an address according to its implementation. A lookup screenshot does not prove which address the player used for its failed request.
Record the hostname, query type, resolver if known and time. If a supported diagnostic exposes the selected destination, keep that separately. Do not infer the chosen family or server from the country's name in an account menu.
Compare repeated results without cherry-picking
Use a small defined set of ordinary authorized attempts, preserving the same item and environment. Note each outcome and its time. Rapid repeated retries can change workload or trigger another limit, so avoid turning a diagnostic into a request flood.
An illustrative name can publish two addresses while one observed connection succeeds and another fails. That warrants an operator check, but it does not prove the addresses are intended to behave identically or that the failure is caused by DNS itself.
Do not pin a guessed address as the repair
Replacing the hostname with a number copied from another attempt can change secure identity and routing. It can also become stale or bypass the operator's intended selection. Use the current approved hostname unless the responsible operator provides a specific supported diagnostic.
A host-file edit can hide a later legitimate change and make future results harder to interpret. Preserve any administrator-led test and restore the intended configuration afterwards. A one-time success through a pinned destination is not a permanent service certification.
Give the operator a useful incident pair
Provide a successful and failed timestamp, player version, safe hostname, actual failed stage and selected address only if legitimately observed and needed privately. Keep full media URLs and tokens out of public reports.
After a correction, repeat the original task under the normal name-based route. A successful lookup alone does not close a connection or media-delivery issue. The useful outcome is a reliable supported request path with publication, selection and application permission treated as separate observations rather than blamed on one convenient DNS screenshot.
Related questions
Does every address in a DNS answer get used by every player?
No. Client selection and connection behaviour vary. Record actual observations rather than assuming a universal sequence.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
