All domains created within virtualmin will have nameservers setuped due to your template settings. So probably all of your domains created in virtualmin will have ns.yourdomain.com and ns1.yourdomain.com - if you have read through how to setup secondary DNS server (it is really simple task). And only what you have to do is to tell your domain registrator that domain which you are registrating has ns.yourdomain.comns1.yourdomain.com nameservers. Then all of DNS records will be handled by those two - and everything is under your control and control of virtualmin.
your registrar tells the root servers in the world where to find your domain or nameservers.
on your box you will then handle all records for a domain. A records, MX records etc.
why 2, see answer in other thread.
the ns2 can be on the same box you have apache running, it can also be on a different box. Up to you, if you can afford it, put it on a different box, in a different location so it will have a different IP.
The second box will then have slave host files as the backup. It is not necessary if you have 1 machine with 20 domains.
You will find the ns2 line in the host file of the domain on your box.
it looks like this:
[code:1]
$ttl 10H
@ IN SOA ns1.domain.nl. postmaster.domain.nl. (
2008063001
4H
1H
1W
10H )
domain.biz. IN NS ns1.domain.nl.
domain.biz. 38400 IN NS ns2.domain.nl.
@ IN NS ns3.domain.nl.
domain.biz. IN A 100.100.100.1
www.domain.biz. IN A 100.100.100.1
ftp.domain.biz. IN A 100.100.100.1
m.domain.biz. IN A 100.100.100.1
localhost.domain.biz. IN A 127.0.0.1
mail.domain.biz. IN A 100.100.100.1
domain.biz. IN MX 5 mail.domain.biz.
domain.biz. IN MX 10 ns3.domain.nl.
domain.biz. IN TXT "v=spf1 a mx a:domain.biz ip4:100.100.100.1 ?all"
[/code:1]
The ns record is not glue. The A record for the NS record is glue