# Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you

**Code:** `dig: status: REFUSED (recursion not available)` · **Category:** Networking · **Seen on:** Linux, Networking

The DNS server answered, but its policy refuses to look up names for your address.

## 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-recursion` limited 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

1. Use a recursive resolver address
2. Add your subnet to `allow-recursion` (BIND) / `access-control` (Unbound)
3. Verify with `dig @server example.com`

## Detailed fix by platform

### Linux

1. 

```bash
dig @203.0.113.53 example.com
# BIND: allow-recursion { 10.0.0.0/8; };
```


## How to diagnose

1. **Server** — Authoritative-only?
2. **ACL** — Includes your network?
3. **Resolver** — Correct in config?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/networking/dns-refused-recursion-denied)