Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm just experimenting with setting up my own name server for my personal domain. I have bind running locally and everything works fine, now I'm at the point where I'm telling my registrar to start sending other requests to it.

My registrar is only interested in the name of my name server, not its IP address. This doesn't make sense to me, as my name server doesn't have a resolvable name, and if it did, who would be resolving it?

I'm trying to minimise my requirements on external infrastructure (for the sake of learning). Can someone please explain this situation to me, and how I might run my website without a 3rd party name server.

share|improve this question
up vote 3 down vote accepted

Every name server must have a resolvable name, because the definition of an NS record requires it, e.g.:

@   IN SOA ( ... )
@   IN NS
    IN NS

ns1 IN A
ns2 IN A

The example above is what's necessary if the hostnames for the name servers for your domain are within the same domain.

However your parent domain (e.g. .com) also needs to know these two IP addresses in these circumstances, so they would also have copies of those two A records above. When a parent zone keeps these records too they're known as "glue records".

In theory, then, your registrar should be asking for the IP addresses but only if the names are within your own domain.

Ultimately a domain look up for would go:

  1. to the root name servers - where is ?
  2. root servers - we don't know - ask the .com servers - they're here (known as a "referral")
  3. to the .com name servers - where is ?
  4. .com name servers - we don't know, but we known what example.coms name servers are, and (this is the important part) - here are their IP addresses
  5. finally your name servers receive the query, and send back the right answer
share|improve this answer

DNS needs what is called a 'glue' record set up so that you can resolve the Master for that domain to its IP address. Your registrar should have instructions on how to setup a glue record within their hosting panel.

for reference: Wikipedia article with information on glue records

share|improve this answer
So when I nslookup, the name server at the top of the internet has a glue record with its IP. And then I use to resolve com. Who owns the server at the top? – Cogsy Nov 9 '09 at 0:54
The servers for gTLDs and ccTLDs (the at the top part - .com, .net, etc) are called ROOT servers are operated for ICANN by different organizations - Verising, Cogent, NASA, ICANN itself to name a few. – Zypher Nov 9 '09 at 3:29
Actually, the gTLD and ccTLD are not on the root servers. Only . is served from the root servers. (and f-root is served by ISC []) – Michael Graff Nov 16 '09 at 0:43

You need to add your hosts by name, first. The registry interface will have an option for this, probably called something like 'Add Host'. It adds them in a special way to the DNS tree so that you can then use them as nameservers.

Once you've added them, you can point to them in the same interface (as you've already discovered) as your name servers.

Sounds bizarre, but it's a basic 'bootstrap' problem.

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.