Skip to main content
HighDNSOWASP A05:2021CWE-200

How to fix: DNS Zone Transfer (AXFR) Allowed from Public IPs

The authoritative nameserver responds to AXFR (zone transfer) requests from arbitrary sources. Zone transfers expose every hostname, IP, and record in the zone to anyone who asks.

Why it matters

An attacker who downloads the full zone file gains a complete map of all hostnames and IP addresses in your domain, including internal services, staging environments, and management interfaces not intended for public discovery.

AXFR is the DNS protocol for transferring an entire zone from primary to secondary nameservers. When enabled without IP restrictions, any Internet host can download a complete inventory of your DNS zone, revealing infrastructure that should not be public.

How to fix it

  1. 1Restrict AXFR to known secondary nameserver IPs in BIND or your DNS provider.
  2. 2Test: dig AXFR example.com @ns1.example.com (should return REFUSED)

Code examples

BIND named.conf

BIND
zone "example.com" {
  type master;
  file "/etc/bind/db.example.com";
  allow-transfer { 192.0.2.10; 198.51.100.20; };  // secondary NS IPs only
};

Test zone transfer

bash
dig AXFR example.com @ns1.example.com
# Should return: Transfer failed. or REFUSED

References

Detected automatically by VulnRadar. The check id is dns-zone-transfer-allowed, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is DNS Zone Transfer (AXFR) Allowed from Public IPs?
VulnRadar rates this high severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-zone-transfer-allowed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does DNS Zone Transfer (AXFR) Allowed from Public IPs map to?
It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for dns zone transfer (axfr) allowed from public ips

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

DNS Zone Transfer (AXFR) Allowed from Public IPs | VulnRadar