I'm new to DNS stuff since I'm in the process of moving my site from shared host to dedicated server on another host and dedicated server host does not provide DNS services.

I also moved to Namecheap as my registrar.

If I understand correctly, I have two options:

1) setup name server on my server and point to it (my server IP as name server) from the registrar. (register name server)

2) Use Namecheap's name servers. (I understand that this option exists from what they write -see below- couldn't find the option on my panel yet)
http://www.namecheap.com/graphics/stock_server-16.gif Free Real Time DNS Servers


Increase the speed and performance of your website by using our geographically dispersed name servers.
Real-time DNS updates with Dynamic DNS option.
You can create up to 50 "hosts", or sub-domains, under your name.
You can also create a catch-all sub-domain.
We provide advanced options so that you can setup all your DNS records like A Address, MX records and CNAME records using our control panel.
My question is :
Which option is recommended , simpler to setup and maintain, has better performance. What is the upside and downside of each.

Also - I have DirectAdmin on my server, Setting up nameserver locally is quite simple but I don't understand whether I should use bind also and what do I have to do on my server for each of the two options above besides using the name server setup option of Directadmin panel.

Thanks!
Nir

One thing is very clear to me - you've got your server too early... People purchasing/leasing dedicated boxes either must have black belt in server's administration themselves or have someone to do this for them. If the person doesn't know how to setup BIND (one of the easiest and widely available solutions) I simply am afraid to even think about security of such server...

Shorter: get a sysadmin. Urgently.

Good luck!

It's probably simpler to set up and maintain using NameCheap's web form.

The advantages are that if your server is down, DNS is still working.

The downside: if NameCheap's DNS infrastructure goes down, you and many others are down.

The downside: if NameCheap's DNS infrastructure goes down, you and many others are down.

1. This is not NameCheap's infrastructure, but eNom's;
2. Having 5 dispersed nameservers (a standart for eNom) it's very unlikely you'll be down...

I would recommend always setting up your own nameservers, mainly for the fact that if you decide to move your accounts elsewhere, it's so much easier than updating all the domains with new nameservers. However, as previously stated, this does pose problems if your ns goes down.

If I understand correctly, I have two options:

1) setup name server on my server and point to it (my server IP as name server) from the registrar. (register name server)

2) Use Namecheap's name servers. (I understand that this option exists from what they write -see below- couldn't find the option on my panel yet)




Demo:Changing DNS for your domain

http://namecheap.simplekb.com/kb.aspx?show=article&articleid=29&categoryid=23



Demo:Creating your own nameservers

http://namecheap.simplekb.com/kb.aspx?show=article&articleid=41&categoryid=23

Two question.

How many domains?
Do you add and remove subdomains

If you talk about a 1-3 domain server with static config. Then stay with Enom.

If you have a lot domains there will be a lot work to admin in 2 different places.
(eg adding a subdomain on host. You have to add that on emon as well.

Hans

Thanks all !

I went for Namecheap DNS and it works beautifully. There is only one domain on my server. I'm not a host company but a single site case.

Thanks again.

- Nir