Custom NS Settings - ns1.mydomain.net, ns2.mydomain.net

[D9R]

(I'm sure this has been answered before but I don't see where.)

If anyone knows anything about setting up custom nameservers I'd appreciate your help.

Let's say that MyDomain.net is one of my domains hosted with DirectAdmin.
I want the nameservers for all of my sites and my clients' sites to be:
NS1.MYDOMAIN.NET
NS2.MYDOMAIN.NET

Where is the best place to assign IPs to them? At the registrar? Or should it (can it) be done at the host?

Currently I have them defined at GoDaddy. Problem is, I'm planning to transfer the domain -- doesn't that mean I'll have to recreate them at the new registrar? And that all the sites using those nameservers will be down during the transition time?

Seems more ideal to have them defined at the host. Is that possible? How?

 

[D9R]

I'm going to venture a guess:

1. They must be defined at the registrar. For example, at the registrar you create one - ns1.mydomain.net - and point it to one IP. Then create the second - ns2.mydomain.net - and point it to the second IP.

2. If I transfer the domain, mydomain.net, to another registrar, the sites using its nameservers won't go offline because the info is cached. As long as I recreate the nameservers immediately after the transfer, things will be fine.

3. But, I still don't understand what is accomplished by creating nameservers in the DirectAdmin control panel.

 

[nobaloney]

You should create custom nameservers at both the registrar and on your DA server.

When you transfer a domain any nameserver information gets transferred with it; you do NOT have to recreate the nameserver registrations at the new registrar.

As to why you'd create custom nameservers on your DA server, that's because in addition to the registration with your domain registrar you also need A records and NS records for your nameservers in your zones, as well as the nameserver assignment in your SOA record.

And you won't get those unless you set up DA to create them.

Jeff