Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

Perhaps I am totally over thinking this but I have a domain name and name servers that are working just fine. I want to transfer the one domain name that I have for my server which is also the name of the nameserver.


with nameservers

I am transfering the from the current registrar to the one I use for all my other domains. The question is what do I have to update? Once the transfer is complete will have and as it's nameservers as it is today. I was wondering though how and are resolving if is pointing to ns1 and ns2. Am I over thinking this or am I missing something in the process here? I always just enter the nameserver names when I configure any domains on my server. Do I have to setup A records somewhere for ns1 and ns2 ?

share|improve this question
up vote 3 down vote accepted

Key item: Since you are only changing your registrar and not the underlying IP addresses associated with your nameservers, this move is transparent.

Be sure to enter glue records (nameserver + IP) at your new registrar. If you are using a primary registrar, I typically see this information show up in the root servers within 5 minutes.

Use a tool like

To confirm things are working as they should.

If your nameserver IPs are changing, then you have other issues to handle, but for a registrar change with no underlying DNS record changes - it is transparent.

share|improve this answer
I think the glue record is the piece I was missing. I just looked that term up and that glue record now makes perfect sense. Thank you! – Mech Software Nov 18 '11 at 18:56

You would want to point your servers to another name server I think, because once they move to registrar they would no longer be serving DNS correct? Just dumb records. I think it's probably safer to rename your domain.internal something though and point to internal dns. Depends on how you were serving DNS on the original servers though.

share|improve this answer
I have no idea which is why I'm asking the question. The DNS server is not moving, only the registrar. – Mech Software Nov 18 '11 at 16:07
Well depending on if internally you need to hit those externals you still might need to add a DNS record, but you should be good :) – LowWalker Nov 18 '11 at 16:10
these are ALL external servers, none are internal. – Mech Software Nov 18 '11 at 16:15

*EDIT: It turns out I'm completely wrong. See the comments. I'd delete this, but I imagine other people might think the same thing I did in answering it, so I'll leave it as a cautionary tale.*

That's an interesting exercise in recursion.

If I understand your question correctly:

You want to have and as its nameservers?

That will not work. You can't have a nameserver in the same domainspace as the domain name.

It's a chicken/egg scenario. When you run a DNS lookup, eventually the nameservers are queried. If is the nameserver for, how do you ever get a lookup for That is - something has to tell you what the IP address is for so that you can query it. If is where you have to go to get the IP address for, how does ever resolve in the first place?

Generally your nameservers need to be in different namespace than the domain they're hosting.

share|improve this answer
Circular dependencies are handled through glue records.… It is quite common for and nameservers to share the same domain. – jeffatrackaid Nov 18 '11 at 16:32
I learn something new every day. Thanks for the update. I would not have thought that'd work. – Driftpeasant Nov 18 '11 at 16:49
+1 for being open enough to admit you were incorrect and leaving it for others to learn from. That's a lesson for all of us. – joeqwerty Nov 19 '11 at 5:01

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.