Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a few domains and want to resolve their DNS records with my own name server. Let's say I have a DNS server with 2 fixed IP addresses and a domain name mydnsservers.net.

I'd like to have 2 name server -subdomains- for my other domains.

  • ns1.mydnsservers.net >
  • ns2.mydnsservers.net >

Can I just use a third party DNS (e.g. AWS Route 53) for mydnsservers.net and setup two A-records like this?

ns1. A
ns2. A

Or is it mandatory to use my own DNS server for mydnsservers.net and configure GLUE records at the TLD registry?

I know that the first option works in some cases, but my new registry gives an error when trying to use ns1.mydnsservers.net for one of the domains because it's not registred as a nameserver (doesn't have glue records).

Any help would be much appreciated!

share|improve this question
How could it possibly work without glue? Say I want to resolve ns1.mydnsservers.net. Telling me that I need to ask ns1.mydnsservers.net for the answer doesn't help me. I need an IP address, and without glue, the only way to get it is by asking the very same servers whose IP addresses I didn't know in the first place! –  David Schwartz Feb 27 '14 at 19:20
I won't be using ns1.mydnsservers.net as a nameserver for mydnsservers.net. Instead, ns1.mydnsservers.net will be resolvable through third party nameservers, not a GLUE record. It works but I guess that's not the ideal way to go? –  Niels L Feb 27 '14 at 21:09
If ns1.mydnsservers.net is not a nameserver for the domain mydnsservers.net, then no glue is needed. If it is, then glue is needed. –  David Schwartz Feb 27 '14 at 21:20
We have a client with a domain example.com. That domain is using ns1.mydnsservers.net as one of the nameservers. The clients domain is resolvable because mydnsservers.net is pointing at an Amazon Route 53 nameserver, which knows what IP belongs to ns1 because of the A record there. So that way, ns1.mydnsservers.net is resolvable without a GLUE record. –  Niels L Feb 27 '14 at 21:26
The IP from ns1.mydnsservers.net belongs to another DNS server that resolves example.com. So actually it has to do 2 lookups.. I guess, without GLUE. –  Niels L Feb 27 '14 at 21:36

2 Answers 2

You need a GLUE record when the nameserver you wish to use for the domain is itself within the domain.

As ns1.mydnsservers.net is within mydnsservers.net, you need a GLUE record.

share|improve this answer
Thanks for your answer. What if you don't use GLUE and resolve ns1.mydnsservers.net externally through third party nameservers? See comments above –  Niels L Feb 27 '14 at 22:17

In certain situations you should be able to set the following at the registrar for example.com

nameserver 1: ns1.someotherdomain.com
nameserver 2: ns2.someotherdomain.com

Now at the DNS servers on ns1.someotherdomain.com and ns2.someotherdomain.com you can set:

example.com.    86400   IN   SOA    ns1.example.com.  root.example.com. 20140827151901 60 120 604800 3
@                       IN   NS     ns1.example.com.
@                       IN   NS     ns2.example.com.
ns1                     IN   A
ns2                     IN   A

The important thing is that there should be a glue record SOMEWHERE in the chain.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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