This is a Canonical Question about DNS glue records.

What exactly (but briefly) is a DNS glue record? Why are they needed and how do they work?

migrated from Sep 9 '11 at 4:24

This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.

up vote 113 down vote accepted

A glue record is a term for a record that's served by a DNS server that's not authoritative for the zone, to avoid a condition of impossible dependencies for a DNS zone.

Say I own a DNS zone for I want to have DNS servers that're hosting the authoritative zone for this domain so that I can actually use it - adding records for the root of the domain, www, mail, etc. So, I put the name servers in the registration to delegate to them - those are always names, so we'll put in and

There's the trick. The TLD's servers will delegate to the DNS servers in the whois record - but they're within They try to find, ask the .com servers, and get referred back to...

What glue records do is to allow the TLD's servers to send extra information in their response to the query for the zone - to send the IP address that's configured for the name servers, too. It's not authoritative, but it's a pointer to the authoritative servers, allowing for the loop to be resolved.

I requested that this answer be merged in from a duplicate question, as the existing answers did not explain the role of the ADDITIONAL section.

To see how it works, type this: dig +trace +additional SOA

This will trace the nameserver authority starting from the root servers (+trace). Adding +additional will also show you the ADDITIONAL section of each DNS server response. Normally most people think of DNS in terms of the QUESTION and the ANSWER sections, but ADDITIONAL also plays an important role: if the nameserver knows the answers to any queries that are related to the answer, it can pre-emptively supply those answers in the ADDITIONAL section without requiring additional queries from your client.

Note that the authoritative nameservers for are rooted under the domain they're authoritative for. (,, etc.)

When you ask a nameserver to supply the list of nameservers for a domain, they will often supply a list of A-type records (IP addresses) in the ADDITIONAL section, not just the NS-type answers: these are called glue records, used to prevent circular dependencies. In this case, those A records are served from the TLD (.com, .org, etc.) nameservers based on the IP addresses that someone supplied the DNS registrar responsible for the domain. They can usually be changed by logging into the admin web interface they supply you.

(disclaimer: AAAA records containing IPV6 addresses can also be supplied as part of the glue, but I left this out for simplicity's sake.)

  • Thank you for the detailed explanation. I've learned a lot. – Egemenk Feb 3 '13 at 14:34
  • Very good explanation. Wish I'd stumbled upon this detail of circular dependency resolution before my last job interview. I'm pretty sure my cluelessness on the subject cost me dearly. – converter42 Feb 18 '15 at 15:43
  • @converter42 To be fair, I don't think most sysadmins actually expect you to get that question right. I'm a DNS lead and I certainly don't. It does tell me when an interviewee knows DNS better than 80% of other admins though. :) – Andrew B Feb 18 '15 at 16:00

There is a precise (and concise) explanation on wikipedia.
To quote:

Circular dependencies and glue records

Name servers in delegations are identified by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred.
If the name given in the delegation is a subdomain of the domain for which the delegation is being provided, there is a circular dependency. In this case the nameserver providing the delegation must also provide one or more IP addresses for the authoritative nameserver mentioned in the delegation. This information is called glue.

. . .

For example, if the authoritative name server for is, a computer trying to resolve first resolves Since ns1 is contained in, this requires resolving first, which presents a circular dependency.
To break the dependency, the nameserver for the org top level domain includes glue along with the delegation for The glue records are address records that provide IP addresses for The resolver uses one or more of these IP addresses to query one of domain's authoritative servers, which allows it to complete the DNS query.

After searching forever and reading a lot about glue records and still not understanding what they were or how you can make them I finally found an answer and it's a very simple one.

As I understand there is no magic extra information sent from somewhere, this is how it works.

Lets say your domain is and you want to use your own name servers and, you need at least two DNS servers.

  • has IP
  • has IP

In order for this to work now you need the top domain owner to put following records into their DNS. NS NS A A

Those two A records are the glue records and they need to be at the top domain, in this case .com, and not all registrars can get this done for you.

If this is wrong please correct me. I just thought I try explain in a simple way for others who can't find correct answer.

  • 2
    The only caveat to your answer is that glue records are not limited to appearing in the top level domains. You can also have a that is delegated to and in the zone. The nameservers for com have delegated away from themselves and cannot provide glue for any of its children. – Andrew B Jun 23 '17 at 20:35
  • 2
    The key point seems to be that without a glue record, if the requested subdomain and name server are underneath the same domain, you will be stuck in an infinite loop: --> --> --> --> and so on – Daniel Waltrip Feb 8 at 20:38
  • I'm having a brain fart and each time I read an explanation of glue I don't quite get enough information - due I'm sure to my lack of knowledge of the meaning of the terms... in this answer when you @hasse when you say "These two A records are the glue records and they need to be at the top domain"... what do you mean exactly by "the top domain"? – Claud Nov 13 at 20:57

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.