Use safely: Follow these steps only for a router or network you own or are authorised to manage. Never send Router Portal a router password, Wi-Fi key, MAC address, serial number or private screenshot.
Evidence and scopeSOURCE-BACKED · CHECK DATE
Sources2 official references
ScopeModel/OS/network dependent
CredentialsNever universal
ReviewRecheck after UI changes
Quick answer: If some names resolve and others time out, compare DNS responses with direct gateway and IP connectivity tests.
What this page covers
Run repeatable, local diagnostics and do not treat changing DNS providers as a universal fix.
Step-by-step workflow
- Test the gateway, a known IP and a hostname separately.
- Use nslookup or dig against the configured resolver.
- Compare wired/Wi-Fi and one alternate authorised client.
- Record timeout, SERVFAIL, NXDOMAIN or refusal results.
Decision table
| Check | What it tells you | Safe next action |
|---|---|---|
| IP works, name fails | Resolution path is the likely branch | Inspect resolver and cache |
| Only some names fail | Authoritative or policy issue may exist | Compare response codes |
| Everything drops | DNS may be a symptom, not the cause | Check link and gateway |
Limits and verification
A public DNS change can hide a local DHCP or security problem. Preserve the original configuration and verify the cause.
Official sources
- Microsoft — Troubleshoot DNS server issues (DNS diagnosis)
- IETF RFC 8415 — DHCP for IPv6 (DHCPv6 behavior)
Related Router Portal guides
Router login troubleshooting · Find the current gateway
Editorial note: This pilot page is written for one distinct question. Firmware, operating-system menus, ISP policies and regional radio rules can change, so confirm the source and exact device before applying a setting.