Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you
The DNS server answered, but its policy refuses to look up names for your address.
status: REFUSEDrecursion requested but not availableDNS query refused;; WARNING: recursion requested but not available Meaning
Authoritative-only servers (and locked-down resolvers) don't do recursion for outsiders. Point clients at a real recursive resolver (your router, 1.1.1.1, 8.8.8.8, or the cloud VPC resolver), or allow your network in the server's allow-recursion / acl settings.
Common causes
- Querying an authoritative-only server as if it were a resolver
allow-recursionlimited to other networks- Cloud VPC resolver not reachable from this subnet
- Access list denying your source IP
- Wrong DNS server in DHCP/static settings
⚡ Quick fix
- Use a recursive resolver address
- Add your subnet to
allow-recursion(BIND) /access-control(Unbound) - Verify with
dig @server example.com
Detailed fix by platform
Linux
- bash
dig @203.0.113.53 example.com # BIND: allow-recursion { 10.0.0.0/8; };
How to diagnose
- Server — Authoritative-only?
- ACL — Includes your network?
- Resolver — Correct in config?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026