A DNS glue record mismatch happens when the address records the parent zone publishes for your nameservers differ from what those nameservers actually answer with, or when the nameservers disagree with each other. Resolvers then get inconsistent or dead answers. Fix it by making the parent glue, the NS sets and the server addresses identical.
Glue is an address record in the parent zone that lets a resolver reach a nameserver whose name sits inside the zone it serves. RFC 1034 defines the delegation model this relies on: the parent holds NS records pointing at the child, and the child is authoritative for its own data.
What causes a DNS glue record mismatch?
Delegation data lives in two places. The parent zone (for example com) holds NS records and, for in-zone nameservers, glue addresses. Your own zone holds its NS set and the A and AAAA records for those servers. Nobody keeps the two copies in sync for you. Common causes:
- You renumbered a nameserver and updated your zone but never updated the glue at the registrar.
- You moved to a new DNS provider and changed NS records in the zone but not at the registry.
- Your servers carry different zone versions because a zone transfer failed or a secondary was left behind.
- A decommissioned nameserver is still listed in the parent delegation and points at an address that no longer answers.
A stale entry looks like this:
; at the parent (registry) - what resolvers are told first
example.com. 172 IN NS ns1.example.com.
ns1.example.com. 172 IN A 192.0.2.10 ; old address
; in your own zone - what is actually true now
ns1.example.com. 3600 IN A 198.51.100.25 ; new address
Some resolvers follow the parent's address, hit a dead host and retry elsewhere. Others trust the child's data. Behaviour varies by resolver software, so the failure is intermittent and hard to reproduce.
Why does it matter, and why is it rated medium?
A mismatch rarely breaks resolution on day one. While one healthy nameserver remains, lookups still succeed, just slower. The risk is a delegation that cannot tolerate another failure. Three weaknesses make it worse:
- Single operator. If every nameserver sits in one network or with one provider, one outage removes the zone entirely.
- Disagreeing servers. If servers return different NS sets, addresses or serial numbers, answers depend on which one a resolver happens to ask.
- Transport and configuration gaps. A server without TCP/53 fails on large responses, including signed DNSSEC answers. An open zone transfer hands your whole zone to anyone who asks. An authoritative server that also recurses can be abused for amplification.
The finding is rated medium because it is a resilience and exposure problem, not a direct compromise. When the last working server fails, the cost is total: web, mail and API names stop resolving, and mail may bounce silently. An auditor flags it because availability is a control objective, and a delegation with no redundancy is a single point of failure.
If the zone is DNSSEC-signed, also check the parent's DS record. Fixing a missing DS record at the parent covers that side of the delegation.
How does the scanner detect and rate this?
SetEnforce queries the parent zone for your delegation, then queries every listed nameserver directly and compares the results. The check looks at:
- NS sets and glue addresses at the parent against the NS sets and addresses each server returns.
- SOA serials across servers, to spot unsynchronised secondaries.
- Whether all nameservers share one network operator.
- Whether each server answers over TCP/53, allows AXFR to arbitrary clients, or recurses for outside clients.
The finding carries medium severity. Its evidence lists the specific discrepancy, such as the parent address versus the address the server reports, or the servers that disagree, so you can see which record to correct.
How do I fix it?
Work from the parent downward.
- Pull the delegation as the parent sees it:
dig +norecurse NS example.com @a.gtld-servers.net
- Ask each listed nameserver for its own view and compare the serials:
for ns in ns1.example.com ns2.example.com; do
echo "$ns"; dig +short SOA example.com @"$ns"
done
- Correct the registrar's host or glue records so they match the real addresses. Remove any server you no longer run. Most registrars call this "host records" or "child nameservers".
- Align the NS set inside your zone with the parent's list, and make sure every server loads the same zone version.
- Spread authority across at least two independent networks or providers.
- Close the transport and configuration gaps. A BIND-style example:
# named.conf options (BIND syntax; other servers differ)
options {
recursion no;
allow-transfer { 203.0.113.53; }; # secondary only
};
Confirm TCP works from outside:
dig +tcp SOA example.com @ns1.example.com
If you publish DANE records, nameserver trouble also affects them. See TLSA records anchored by an unsigned zone for why this matters to mail.
How do I confirm the fix on re-scan?
Parent changes honour the parent's TTL, so wait for the old values to expire before judging the result. Then re-run the dig commands above and check that:
- The parent NS list equals the zone's NS list.
- Every glue address equals the address the server reports.
- All servers return the same SOA serial.
- TCP queries succeed, a transfer request from an outside host is refused, and the server does not recurse for strangers.
Then trigger a new scan. The finding clears when the parent and child views agree and the delegation spans more than one operator. If it persists, the evidence shows which record still differs.
Common questions
How long does a glue fix take to propagate?
Registry changes usually publish within minutes to hours, but resolvers cache the old delegation until its TTL expires. TTLs on parent delegations are often a day or more, so allow that long before concluding the fix failed. Lowering TTLs before planned changes shortens the wait.
Do I need glue records at all?
Only when a nameserver's name sits inside the zone it serves, such as ns1.example.com for example.com. Otherwise resolvers can look up the address independently. Using nameservers under a different domain avoids glue maintenance, though it adds a dependency on that domain staying healthy.
Can a mismatch be exploited by an attacker?
It is mainly an availability risk, but related gaps are abusable. An open zone transfer reveals your hostnames, and an abandoned nameserver address that someone else acquires could answer for your zone. Keeping the parent delegation clean closes both openings.
Key takeaways
- A DNS glue record mismatch means the parent's delegation data and your nameservers disagree, which fails unpredictably across resolvers.
- It is rated medium because the damage is total only once redundancy runs out, and that moment is hard to predict.
- Fix the registrar glue first, then align NS sets and zone versions, then diversify operators and harden transport.
- Verify with dig against the parent and each server, then re-scan after TTLs expire. SetEnforce checks the delegation, glue consistency, operator diversity, TCP support, transfers and recursion in one pass.