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 unix.stackexchange.com Sep 9 '11 at 4:24
This question came from our site for users of Linux, FreeBSD and other Un*x-like operating systems.
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
There's the trick. The TLD's servers will delegate to the DNS servers in the whois record - but they're within
What glue records do is to allow the TLD's servers to send extra information in their response to the query for the
There is a precise (and concise) explanation on wikipedia.
I requested that this answer be merged in from a duplicate question, as the existing answers did not explain the role of the
To see how it works, type this:
This will trace the nameserver authority starting from the root servers (
Note that the authoritative nameservers for
When you ask a nameserver to supply the list of nameservers for a domain, they will often supply a list of
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 example.com and you want to use your own name servers ns1.example.com and ns2.example.com, you need at least two DNS servers.
In order for this to work now you need the top domain owner to put following records into their DNS.
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.