Setting NS1, NS2, how to? Can't find it in manuals

Under webmins modules - networking- Network Configuration-
click on network interfaces.
You will see your IP bound to eth0
You have to add an interface and call it eth0:1 - fill in the proper info like a different IP you got from the datacenter.

The eth0:1 will be a virtual interface.
Repeat this but name it eth0:2 and use another IP you received from the datacenter.

It will look like this
Name Type IP Address Netmask Activate at boot?
eth0 Ethernet xx.xxx.130.15 255.255.254.0 Yes
eth0:1 Ethernet (Virtual) xx.xxx.130.149 255.255.254.0 Yes
eth0:2 Ethernet (Virtual) xx.xxx.130.150 255.255.254.0 Yes

click - Return to network configuration then click on - Host Addresses

I have added the 2 new IP's to the HOST adresses
xx.xxx.130.149 ns1.mydomain.nl , ns1
xx.xxx.130.150 ns2.mydomain.nl , ns2

Then you need to click "Apply configuration" NOTE: if you made a mistake, it is possible to loose connection to the server. So I advice to be careful and double check your settings 5x before hitting that button.

At the registrar you need to change and add the A records for you main domain.
In my case mydomain.nl I have this:

A ns2.mydomain.nl -> xx.xxx.130.150
A *.mydomain.nl -> xx.xxx.130.15
A mydomain.nl -> xx.xxx.130.15
A ns1.mydomain.nl -> xx.xxx.130.149
A sv01.mydomain.nl -> xx.xxx.130.15
MX-5 mydomain.nl -> sv01.mydomain.nl

CNAME pop3.mydomain.nl -> sv01.mydomain.nl
CNAME mail.mydomain.nl -> sv01.mydomain.nl
CNAME smtp.mydomain.nl -> sv01.mydomain.nl
CNAME pop.mydomain.nl -> sv01.mydomain.nl
PTR sv01.mydomain.nl -> xx.xxx.130.15

sv01.mydomain.nl is the systems name obviously.

hope that helps.
Oh and then you need to add to the servers template under -BIND dns domain- fill in in the empty big box:
${DOM}. 38400 IN NS ns2.mydomain.nl.
Note include the dot at the end of that line!

replace mydomain.nl with the domain you are actually using :P

Joe, out of curiosity, because I was convinced (after reading much documentation on the subject) that you need to register your nameservers (machines) at the domains registrar. Now my registrar doesn't offer such service so I couldn't (hence the A records)

I can however change the nameservers at my registrar for my main domain, but who is gonna know about them if they aren't listed? Also to register the nameservers (machines), normally, you'll need 2 of them in different networks.

I'm confused again :/
I think my confusion is found in nameserver as in a machine (and you'd have to pay a fee to get that machine listed somewhere as a nameserver) and nameserver as in the local BIND

For example:
my server is called sv01.mydomain.nl
I can change the ns records for mydomain.nl at my registrar to ns1.mydomain.nl and ns2.mydomain.nl and point them with the IP to my machine.
The ns1 and ns2 are running on sv01.mydomain.nl but since sv01.mydomain.nl isn't listed as a nameserver, would that not become a problem?

The way I did it now also allowed me to point an A record at my registrar to a second server in a different network which is acting purely as a slave nameserver.

Or is listing the machines not necessary at all?

Ronald's method of adding IPs will work fine.

However, you said:

<div class='quote'>1) I heve one default IP address set, but I want to add more IPs to system which I already received from datacenter, I tried &quot;System Settings&gt;Shared IP Addresses&quot;, but it's not possible.</div>

You don't necessarily need to do anything to &quot;add&quot; them to your system--just use them when you need them. So, when you create a new virtual server, just choose to have it on its own IP and fill in the form.

But, if you'd rather the addresses be pre-existing, you can do that to, as Ronald said.

<div class='quote'>2) when I have this ready, I want to use 2 IPs from these added, and create DNS with my domain name (ns1.DOMAIN.com, ns2.DOMAIN.com)</div>

Ronald is on the right track with his registrar advice, but all of the A records are unnecessary if you're going o have your own name servers. Running your own is the easiest to manage, since Virtualmin can manage the A records and MX records and everything else for you, once you make the registrar aware of your name server(s).

GoDaddy is extremely irritating when it comes to spinning up a new nameserver from scratch--your name server needs to already exist in some zone that is hosted on some other name server, because GoDaddy doesn't have a field for filling in the IP address (like many registrars offer).

What this means is that you need to have <i>another</i> name server that is already working and you can add records to, and you need to add your new server it. Then you can give GoDaddy the address you've just created for your name servers for your new zone...once that one exists and is resolving you can change the GoDaddy glue records to point to the new ns names.

Confused yet? Yeah, me too. Go yell at GoDaddy for being a wee bit stupid.

Basically, you need an existing name server before you can create name servers for domain names hosted with GoDaddy. GoDaddy's own free DNS hosting will probably work for this purpose, though, so you can probably spin it all up entirely from within GoDaddy's interface.

But this is almost entirely outside of the scope of Virtualmin. Once your glue records are right at your registrar, you just need to create two NS records in your domain using the BIND module in Webmin...which I think is pretty easy, and documented in the Webmin wiki:

Adding records is covered here:

http://doxfer.com/Webmin/BINDDNSServer#Adding_and_editing_records

And the types of records are documented here:

http://doxfer.com/Webmin/BINDDNSServer#Record_types