Migration of DNS management to DA + "local mail"

[webunity]

Currently i have all my domains registered somewhere and they offer a user interface for DNS management. Super easy!

Now i've moved several domains already, skipping mail for now, and one of those domains brought to light that sending email from PHP to @domain.com does not work.

This was fixed by setting "local mail server" to false. DNS control had to be switched on for that (which i find strange) before i could change that, and it does not seem to be a template setting (neither "local mail" or "dns control").

That being said; i would like to start using DA for DNS management, so my clients can do their own configuration right in DA like it is supposed to be.

Few questions arise:
1) Do i have to enable "DNS control" manually for all my currently moved domains? Or is there a quick way to do this?
2) Is there a 'master setting' to do this automatically for newly created domains? Since it does not seem to be in the template.
3) After setting 2 nameservers in DA (which need to be the secondary ones according to my hoster), how do i find out at which IP DA is currently running DNS?
4) And knowing (3) can i then just switch the nameservers from one of my moved domains to that DA ip and everything will be ok?

 

[webunity]

I can't edit my thread; but i've managed to find the DNS control setting. It was disabled for my reseller. Enabling it and updating the user packages turned it on for all users.

Question 1 and 2 are answered.

 

[nobaloney]

3) After setting 2 nameservers in DA (which need to be the secondary ones according to my hoster), how do i find out at which IP DA is currently running DNS?

DirectAdmin will use your main (server) IP# to send out all DNS requests, and it will answer DNS requests on all working IP#s.

4) And knowing (3) can i then just switch the nameservers from one of my moved domains to that DA ip and everything will be ok?

First make sure your zone files are properly set up on your DirectAdmin server.

Then you must enable domain servers at your registrar.

For example, if you're going to use ns1.you.com and ns2.you.com, then you must go to the registrar for you.com, and enable two nameservers. This is NOT the same as telling the registrar which nameservers to use. If you're buying domain registration from me, the setting is called Child Nameservers; other registrars may vary and you may need to contact your registrar's support department.

If you're going to use separate nameserver names for each of your domain; for example use ns1.example1.com and ns2.example1.com as namesers for example1.com, and similarly for each separate domain, you need to do this for all domains.

I don't recommend this; I'd say use ns1.yourcompanyexample.com and ns2.yourcompanyexample.com for all domains hosted on your server.

Once you've done that, then you need to assign your nameservers for the domain at yor registrar. That's generally much easier to do at your registrar; much easier to find .

Do this for each domain you're hosting.

I don't think I've left anything out; anyone else feel free to add to this thread .

Jeff