I think you are in part confused by the term "glue". There is no "glue" record type in the DNS, that kind of records do not exist. What we do reference there are purely
AAAA records. They are called "glues" because they exist at the parent side of the DNS delegation, instead of at a child, where expected.
They exist only to aid resolution, they are not authoritative. But without them, there would be a chicken and egg problem.
Let's go back to basics.
Say you want to have domain
example.com served by nameservers
When you register domain names, through a registrar, you provide various administrative details and for the technical part you provide the domain name obviously and its list of nameservers. The registrar sends all that to the registry, and normally, DNS wise there is only a single thing appearing as consequence: the registry publishes in its authoritative nameservers some
NS records that will tie your domain name to your nameservers by letting any resolver asking that there is a zone cut, that is the registry says, with those
NS records: I know nothing more about
example.com because this name is handled by such and such resolvers, hence go query them for additional details.
This is all fine, if your
example.com domain was using
ns2.provider.example nameserver the delegation would work as is, and the resolver would then continue by first trying to find out the IP address for the name
ns1.provider.example (or the other one) and then query that nameserver for further information.
But let us go back to our example which would mean the registry is publishing this:
example.com. NS ns1.example.com.
example.com. NS ns2.example.com.
which is to say for the registry it will reply: please go ask
ns1.example.com for more information on domain name
example.com, but to do so a resolver will then need to get the IP address of
ns1.example.com and hence it is now in a loop with no exit as it goes back to first point to get information on
This is where glue records exist and they break the loop.
Because when you (through your registrar) will create nameserver
ns1.example.com you will be forced to provide an IP address (one or more, IPv4 or IPv6 of course), and same for other one. Those IP addresses will be published by the registry because they are needed for the resolution to happen. Those records are called glue records, but they are normal
AAAA records just sitting on registry authoritative nameservers.
Those records also need to exist on your nameservers (that is if you query directly
ns2.example.com) so the same exact records (of course the IP addresses must match on both sides otherwise you create havoc, and it is a known and frequent source of problems) in fact exist on both side of the delegation cuts. They would normally exist only on the child (delegate) side, but they are needed on the parent for the resolution to work, and to discriminate, on the parent side they are called "glues".
Your registrar (not registry, you never interact directly with registries, registries customers are registrars not end clients, with some exceptions for some TLDs like
.de) should be able to explain all of this to you. Its interface or API should be able to let you create nameservers with IP addresses when needed (the above is a summary there are various other edge cases, like when you change the name of a nameservers, which is allowed normally, or when you associate/dissociate those nameservers with existing domains), so that the registrar sends the appropriate content to the registry.