Direct answer
Partial DNS failure can involve a resolver, VPN/filter, IPv6 path, stale cache or the site itself. Compare hostname lookup with direct access and another resolver/network.
What this covers
- The observed symptom matches this record
- Customer-accessible settings, connections and external components
- Diagnosis before reset, deletion or component replacement
What it does not cover
- ×A model-specific error code with a different documented meaning
- ×Internal electrical, battery-cell, gas, refrigeration or sealed-component repair
- ×A guarantee that every model exposes the same control label
Capture the exact symptom
ReversibleRecord the exact browser error and test the same domain on another device and cellular network.
Run the smallest isolation test
ReversibleDisable VPN/content filters for one test, restart the client and query the router/provider and a reputable alternate resolver.
Correct only the proven cause
ReversibleCorrect the failed filter/resolver or update router firmware; avoid permanent changes based on one unavailable site.
Verify before changing anything else
ReversibleLoad several previously failing domains after cache expiry and restart.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Exact questions
Common follow-ups
What should I check before resetting anything?+
Record the exact browser error and test the same domain on another device and cellular network.
What is the safest isolation test?+
Disable VPN/content filters for one test, restart the client and query the router/provider and a reputable alternate resolver.
When should I stop troubleshooting?+
Managed networks may enforce DNS for security; get administrator approval before changing it.
Answer for the exact device and software version shown above.