Move Main DNS Records to Service Provider

pnode

Verified User
Joined
Dec 2, 2007
Messages
27
Is it wise to move primary dns records from server to domain provider like resellerclub ?
I have several machines where their names are a.domain.com b.domaim.com and so on.
So when my main dns server down i can not reach other servers via name.

Is it wise to move domain.com dns records to domain provider like resellerclub ?

Thanks
 
If you have multiple servers all with DA, you should use the multi-server function to duplicate DNS to all servers you connect with that function.

Once done, you can set a single nsX DNS for each host you "connect" and change nameservers at registar, so, if one server is down, other nameserver will keep responding and provide DNS.

Regards
 
If you have multiple servers all with DA, you should use the multi-server function to duplicate DNS to all servers you connect with that function.

Once done, you can set a single nsX DNS for each host you "connect" and change nameservers at registar, so, if one server is down, other nameserver will keep responding and provide DNS.

Regards

Thank you for the response.

Right now we also have non da servers with same main domain name.
For example da servers are a.domain.com b.domain.com but also i have other servers with c.domain.com and so on.
ns1.domain.com and ns2.domain.com is on the machine a.
ns3.domain.com and ns4.domain.com points to machine b.
When machine a is down, i can not reach other other machines as the main dns server for domain.com is machine a.

I thought i can move dns management of only domain.com to resellerclub where i point every single subdomain, ns to related server.
With this way i can solve the failure of main dns server.

Is it possible ?
 
You can also add DNS in DA for domain not hosted, in admin dns settings, at the end of the page you can add a domain, an IP, and two nameservers

I would suggest you to "merge" all DNS management to DA, than use multi-server setup with DA servers and, if you have non-DA servers, you should also consider to put DirectSlave in them to have other DNS servers that are synced with DA using the multi-server setup aswell.

For example, in your case you have 2 DA Server and 2 NON-DA Servers, so:
ns1 - DA Server
ns2 - DA Server
ns3 - NON-DA Server
ns4 - NON-DA Server

ns1 and ns2 can be connected with multi-server setup themself
ns3 and ns4 can be connected with ns1 and ns2 using DirectSlave and DA Multi-Server Setup

With this, you will have the ability to set 4 NS to each domain, ns1 ns2 ns3 ns4 (usually 3 are enough).

You can also move DNS management elsewhere (resellerclub in your example), but my opinion is that have a single way to mange all domain's dns is much better and easyer, but that's up 2 you definitly

Regards
 
You can also add DNS in DA for domain not hosted, in admin dns settings, at the end of the page you can add a domain, an IP, and two nameservers

I would suggest you to "merge" all DNS management to DA, than use multi-server setup with DA servers and, if you have non-DA servers, you should also consider to put DirectSlave in them to have other DNS servers that are synced with DA using the multi-server setup aswell.

For example, in your case you have 2 DA Server and 2 NON-DA Servers, so:
ns1 - DA Server
ns2 - DA Server
ns3 - NON-DA Server
ns4 - NON-DA Server

ns1 and ns2 can be connected with multi-server setup themself
ns3 and ns4 can be connected with ns1 and ns2 using DirectSlave and DA Multi-Server Setup

With this, you will have the ability to set 4 NS to each domain, ns1 ns2 ns3 ns4 (usually 3 are enough).

You can also move DNS management elsewhere (resellerclub in your example), but my opinion is that have a single way to mange all domain's dns is much better and easyer, but that's up 2 you definitly

Regards

Thank you very much for detailled response.
I will be trying to implement your method.
 
Is it wise to move primary dns records from server to domain provider like resellerclub ?
I don't think this specific question was ever answered, and for the benefit of Googlers who end up here I thouught I'd add this bit of information.

The advantage of using DirectAdmin's built-in nameserver(s) to manage your domain(s) is that they get updated automatically when you add or change domains on your server.

If you're using outside nameservice, such as that provided by ReselerClub or others (including even NoBaloneyDomains :) ) you'll have to update them yourself.

You should definitely use multi-server option if you have multiple nameservers; if you don't you can use it with DirectSlave (search these forums) with your own non-DirectAdmin server used for slave DNS. Or if you don't want to run yor own slave DNS servers you can get slave DNS from others, including me, as a commercial service.

Jeff
 
Back
Top