To the subject of the thread I could say the following (here and below I express my own opinion on the question, and my point of view might differ from others):
1. I don't like an idea of using MySQL on a remote server, unless you're managing a high-load project with thousands of hits per second/minute. Using of a remote MySQL server might be justified if you need a MySQL cluster, which consists of several servers.
If you've got more than 1 server with let's say 1000 users on each, then in case if MySQL gets unavailable on one server, sites get down also on only one server, and you'll get complains only from <1000 users, as a contrast of <2000 complains in case you've got MySQL as a remote service on a server which goes down for any reason.
2. Using of a remote PO3/SMTP server might be not a bad idea, but directadmin is not designed for that, and in this case you'll need a serious customization. Thought there are some users on the forums who are managing similar infrastructures, I'd personally would not for my own needs (at least for now).
3. Regarding external DNS, I've already posted in a similar thread on the forums.
And again, here above there is only my own point of view based on my understanding of the subject and experience of using Directadmin on servers for shared hosting as well as on single project servers. And as I offer a commerce service of server administrating, my customers might have another opinion on the subject, and in this case I'll be happy to assist them to achieve the desired.
P.S. By the way from my own experience it might be a good idea to use a remote SMTP server as a relay for sending OUT emails from your hosting servers, as in this case you are able to control outgoing emails and to do additional antivirus and antispam checks (of course if it is legal in your country and is allowed by your TOS).