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: The response code changes what the resolver is telling you: a name may not exist, the resolver may be unable to complete the query, or the path may be silent.
What this page covers
Interpret the response code with the queried name, server and time—not from a browser error alone.
Step-by-step workflow
- Repeat the query against the configured resolver.
- Check the exact hostname and search suffix.
- Compare an authoritative or documented alternate resolver only for diagnosis.
- Keep the output private if it contains internal names.
Decision table
| Check | What it tells you | Safe next action |
|---|---|---|
| NXDOMAIN | The queried name was reported as nonexistent | Check spelling and DNS zone |
| SERVFAIL | Resolver could not complete the query | Inspect upstream/validation path |
| Timeout | No timely response was received | Check firewall, path and server load |
Limits and verification
A single response cannot prove an outage or attack. DNS records and caches change over time.
Official sources
- Microsoft — Troubleshoot DNS server issues (DNS diagnosis)
- IETF RFC 2131 — Dynamic Host Configuration Protocol (DHCP message and lease concepts)
Related Router Portal guides
Router login troubleshooting · Router security guide
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.