When only one device cannot resolve names, start with that device's configuration and path rather than changing DNS for the entire home. A working phone shows that some network access exists; it does not establish that the affected endpoint uses the same resolver or network.
Keep the symptom at the name-resolution stage. An application saying “network error” may also mean a failed connection or rejected request, so look for the actual error detail.
Compare like-for-like configuration
Check the affected device's active interface, local address, gateway and resolver through supported menus. Compare a working device on the same intended network. A guest network, manual DNS entry or stale static configuration can make the two endpoints less comparable than they appear.
If several adapters are active on a computer, identify which one the task uses. A cable connection and Wi-Fi connection can have different configurations. Do not copy another device's IP address; duplicate addressing creates a separate problem.
Test an independent name
Use a supported lookup tool where available to query both the affected hostname and an independent legitimate hostname. Record the resolver and response. If the device has no diagnostic tool, use its supported internet test and report that the exact DNS stage remains unconfirmed.
A failed lookup for one name can concern that domain's records or policy. Failure for all names can point to the resolver path or local configuration. Neither finding alone proves that the media provider is down.
Inspect local overrides and cached results
A manually entered resolver, local hosts entry or application-specific setting can affect one device. Review only the configuration you manage, and preserve the baseline before changing it. Microsoft documents how Windows displays resolver configuration and cached entries; other platforms have different supported routes.
Clear a relevant cache only if the evidence warrants it, then repeat the same lookup. Do not combine that with deleting player data, replacing account details and rebooting every router. Several simultaneous changes leave no reliable explanation for a later improvement.
- Confirm the actual error stage and active interface.
- Compare addressing and resolver settings on the same network.
- Test the affected and an independent name.
- Review supported local overrides or cache evidence.
- Make one reversible correction and verify the original task.
Escalate the narrow result
If the endpoint still fails while comparable clients resolve the same name through the same intended path, provide the device's redacted configuration and observed errors to its support channel. Include the time and successful comparison.
If a different network changes the result, record that without declaring the home resolver universally broken. The alternate network changes several variables. The goal is a reproducible account of which device and name fail, not a broad claim based on one successful phone test.
Useful answers
Should I copy the working phone’s IP address?
No. Each endpoint needs its own valid assignment. Copying an address can create a collision; compare configuration roles instead.
Does a “network error” always mean DNS failed?
No. It can refer to later connection or application stages. Use specific diagnostics or acknowledge that the exact stage remains unconfirmed.