The Availability and Security Implications of Glue in the Domain Name System

Zheng Wang

Abstract

The Domain Name System (DNS) is one of the most fundamental components of the Internet. While glue is widely used and heavily relied on in DNS operations, there is little thinking about the necessity, complexity, and vulnerability of such prevalent configuration. This work is the first to provide extensive and systematic analysis of DNS glue. It discusses the availability implications of glue and proposes the minimum glue records in terms of availability. It also identifies the security vulnerabilities of glue as well as the limitations of current countermeasures. Measurements show the wide occurrences of glue redundancies and glue vulnerabilities.

The Problem: The DNS "Chicken-and-Egg" Dilemma

In the DNS hierarchy, "glue" records are the IP addresses of nameservers provided by a parent zone (like .com) to help a resolver find a child zone (like example.com). Without glue, the system faces a cyclic dependency: to find the IP address of ns1.example.com, a resolver would first need to query ns1.example.com itself.

Cyclic dependencies across three zones (com, net, and org) illustrating the necessity of glue records to break resolution loops.

Despite being a cornerstone of Internet routing, glue is often misunderstood and inconsistently implemented. This research addresses three main gaps: identifying the minimum glue required for availability, analyzing how different DNS implementations handle "bailiwick-checking" (verifying glue legitimacy), and exposing why DNSSEC fails to fully protect these records.

Methodology

The study employed a multi-pronged approach to evaluate the DNS glue landscape:

  • Theoretical Modeling: Deriving the minimum set of glue records required to break cyclic dependencies in complex multi-zone scenarios.
  • Implementation Analysis: Comparing the source code and behavior of major resolvers—BIND, Unbound, and MaraDNS—regarding their caching and trust logic for glue.
  • Protocol Analysis: Identifying "glue redirection attacks" that exploit features like NSEC3 Opt-Out in DNSSEC, which allows for "signed insecure zones."
  • Empirical Measurement: Analyzing a dataset of 1,070 large industrial US domains (Fortune 1000) and the Alexa Top 100 to measure real-world redundancy and vulnerability.

Key Insights: Security Blind Spots

The "Bailiwick" Confusion

There is no single standard for what constitutes "in-bailiwick" glue. While BIND is strict, other implementations like MaraDNS are loose, accepting nearly any domain-to-IP mapping provided in a referral. This inconsistency creates a significant attack surface.

The DNSSEC Gap and Redirection Attacks

Glue records in a parent zone are not signed by DNSSEC. Consequently, a resolver must perform separate authoritative lookups to verify glue, which many fail to do correctly. The most striking insight is the "glue redirection attack," where an attacker manipulates NSEC3 proofs to trick a resolver into treating a legitimate domain as an insecure delegation, redirecting traffic to a malicious nameserver.

A glue redirection attack where a resolver is tricked into accepting a bogus IP address for a nameserver, leading to a malicious server.

Key Results and Empirical Findings

  • Widespread Vulnerability: Nearly 50% of the measured domains were found to be "glue forgeable," primarily due to reliance on unsigned glue records.
  • Excessive Redundancy: 98.3% of "possibly excessive" glue records were found to be unnecessary for resolution. Rather than increasing resilience, this redundancy increases the attack surface for configuration errors and inconsistent data.
  • Implementation Divergence: Unbound proved to be the most restrictive, while BIND and MaraDNS took varying risks with caching unverified glue.
  • Low DNSSEC Adoption: Only 1.6% of the large industrial domains analyzed were signed with DNSSEC, leaving the vast majority of the web exposed to these vulnerabilities regardless of DNSSEC's internal limitations.

Conclusion and Future Work

The study highlights that glue, while essential for availability, remains a significant security weakness. Future work should focus on developing standardized, robust bailiwick-checking algorithms and investigating the added complexity of IPv6 (AAAA records) on the delegation chain. Furthermore, addressing the NSEC3 Opt-Out vulnerability is critical for securing Top-Level Domains (TLDs) without compromising performance.

Summary updated

Abstract

The Domain Name System (DNS) is one of the most fundamental components of the Internet. While glue is widely used and heavily relied on in DNS operations, there is little thinking about the necessity, complexity, and venerability of such prevalent configuration. This work is the first to provide extensive and systematic analysis of DNS glue. It discusses the availability implications of glue and proposes the minimum glue records in terms of availability. It also identifies the security vulnerabilities of glue as well as the limitations of current countermeasures. Measurements show the wide occurrences of glue redundancies and glue vulnerabilities.
BibTeX
@misc{wang2016availability,
  author = {Zheng Wang},
  title = {{The Availability and Security Implications of Glue in the Domain Name System}},
  year = {2016},
  eprint = {1605.01394},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/1605.01394},
}

Loading related content...

Figure