If you want to use it as a DNS server for your domains, you need to create records on the machine for the domains that you want. This can be done in the DNS section of the web interface. Just use the wizard, it will give you all of the records that you need. Once that is complete, you can dig your domain at the NameServer IP. Code: dig @ 12.34.56.78 example.com This will show you the records that are being handled by the server for that domain. The last thing that you need to do is set your domain's nameservers to the nameservers that you have created. That should be it. Let me know if you need anything else.
Did you create A records at the registrar for the nameserver? You have to create the host, but you also have to make the A record as one of your records through them. I know that adding the A record in at GoDaddy allowed me to get my ns1 and ns2 up. The host were there, but the A record stopped the whole thing.
You need to add a the A record for ns1 at your registrar. Who is your registrar? In most cases, you have to register a Host with them, and you have to create the A record to point to the host.
The reason is the hen <==> egg problem. How should the world know the ip of your nameserver, if you defined the ip on your nameserver? So the A-record for the hostname of the nameserver itself has to be defined at the registrar. Thats named glue records, see wikipedia: http://en.wikipedia.org/wiki/Domain_Name_System
Depending on who it is, you have to also put a records for ns1 and ns2 in the A records section. That is what I am trying to get you to do. If you did not put those in, it will not work.
So your site just shows a blank page? Either way, I was telling you the right thing. You can read Till's post above. You have to register the A record of the nameservers with your registrar, whether or not you want to believe it.
I hope that you realize that your nameserver is not answering this request. Ns2.afraid.org is. Your nameserver is not working.