Follow the local and remote steps
A device can resolve a public hostname yet still have a local path problem reaching its gateway. It can also reach the gateway while name resolution fails. Those observations belong to different stages and should not both be called DNS trouble.
IPv6 uses neighbour-discovery mechanisms rather than ARP for its relevant local-link functions. Do not apply an IPv4-only diagnostic label to every address shown on a dual-stack device. Keep the actual protocol and interface context.
Use actual state, not an empty-list assumption
A neighbour cache is dynamic. An absent entry at one moment is not by itself proof of a fault, and a remembered entry is not proof that the neighbour is currently reachable. Tools and operating systems expose state differently.
An illustrative television can have a correct DNS answer while an unavailable local gateway prevents its media connection. Changing the account password will not restore that local path. Another client can reach the gateway but fail a hostname lookup, requiring a different next test.
Avoid indiscriminate clearing
A supported cache refresh can be useful for a defined diagnostic question, but clearing every network cache and rebooting all equipment together destroys useful attribution. Preserve the original symptom and compare one relevant change.
Do not copy hardware-address entries from another customer's network or install tools promising to repair every neighbour automatically. A duplicate-address or local configuration problem needs the network administrator's actual evidence and supported correction.
Return to the original request ladder
Verify local access, external routing, name resolution and the actual player action as distinct observations where tools permit. Record the first failed stage and one working comparison. A successful local neighbour exchange does not establish remote account authorization or source availability.
Keep diagnostic exports scoped because they can identify household devices and traffic. Support usually needs the relevant interface, time and outcome rather than a public full neighbour table. The useful distinction directs attention to the correct address-resolution layer and avoids turning a familiar cache-clearing command into a universal streaming remedy.
Related questions
Does clearing DNS remove every local hardware-address association?
No. DNS and local neighbour resolution are different systems with different state and controls.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
