is it also necaserry to point the two ns1. ns2. "nameservers" to my VPS.
You don't say whose nameservers you're using now, but if they belong to your old webhosting company and you're going to leave them, then you must change your nameservers to point to (a) your server (ns1), and optionally but recommended, (b) to at least one other nameserver which you've arranged to have used as a slave DNS server, hosting DNS (ns2).
If you're using DNS at your registrar, then it's safe to change all the DNS records at your registrar to the IP#s needed for your old services to your VPS; thouse should continue to work unless you move your domain to another registrar.
However it's certainly easier to simply point your nameservers to the new VPS and let DirectAdmin handle the zones. Just keep in mind that you must do that not only on the new VPS, but also at the registrar.
First you must
Register a NameServer and it requires that you enter nameserver names for both ns1 and ns2, for example, ns1.example.com, and ns2.example.com, and their IP#s (if you've got one VPS and only one IP# then both must use the same IP#, but then you've got no DNS redundancy).
Afterwards you need to assign the nameservers to the domain at the registrar. These are two completely different operations.
Once they're done, your domain will be pointed to your new nameservers and DirectAdmin will manage them.
There's a lot of good information at the DirectAdmin Site-Helper
site (site-helper.com), the help system site developed by the developers and publishers of DirectAdmin. My company hosts tutorials for some specific registrars, for use by my clients, on my tutorials page (still under construction as of this writing)
here (nobaloney.net). My tutorials may not show any information for registering nameservers at all the registrars; I don't remember and haven't checked in a while. If you're not sure, ask your registrar.
While this sounds more complex than simply changing zones at nameservers at your registrar, it's easier in the long run for most people.
The record name in Domain Panel is already set, and cannot be edited. Without the "DOT" behind .nl
And in VPS Dns Settings I want to copy, it has a "DOT" behind .nl, so it looks like this: .nl.
Just don't worry about it? Please explain to me.
I'm not sure what you mean by
Domain Panel but if you mean in DirectAdmin when you look at the DNS zones, then the '.' always needs to be there because nameservers require it at the end of every fully qualified domain name; for more information, see
this (dns-sd.org).
Jeff
