When every device behind a MikroTik router fails DNS lookups at the same time, the fault is almost certainly in the router’s own DNS configuration rather than on individual client machines.
DNS translates domain names into IP addresses — a router that handles DNS for its LAN needs both valid upstream DNS servers configured and permission to answer queries from client devices.
Common Symptoms
- All LAN devices can ping IP addresses but not domain names
- nslookup fails from every device on the network
- Some websites load (cached) while new ones fail to resolve
Possible Causes
- No DNS servers configured on the router
- “Allow Remote Requests” disabled, so clients using the router as DNS get no response
- Upstream DNS servers unreachable or blocked
Before You Begin
Method 1 — Set reliable DNS servers
Configure DNS servers
IP → DNS — set servers to a reliable public resolver like 1.1.1.1 and 8.8.8.8 if not already configured.
Method 2 — Enable remote requests
Method 3 — Test resolution directly from the router
Run a DNS test
Use the resolve command shown below from the router terminal to confirm the router itself can reach and use its configured DNS servers.
Useful Commands
:resolve example.comFrequently Asked Questions
Should clients use the router or a public DNS server directly?
Either works; using the router as a local resolver with “Allow Remote Requests” enabled can add local caching benefits, while pointing clients directly at a public resolver is simpler to troubleshoot.
Conclusion
A missing DNS server entry or a disabled “Allow Remote Requests” setting explains the vast majority of network-wide DNS failures on MikroTik.
Related Articles
