They told me to use my server IP address, but my domains are with <domain registrars> which require two unique NS fields (NS1 and NS2), so that doesn't work.
I am very confused. Have called tech support 6 times and get a different answer each time.
So my question is, how to I manage my own DNS on a dedicated server?
[edited by: Webwork at 2:37 pm (utc) on Feb. 21, 2006]
[edit reason] Generalized [/edit]
if you just want to run a dedicated web server, then what you can do is: use your registrar's dns servers and just set the A record on the registrar's dns server to point to your dedicated IP address of the dedicated server at your hosting company.
I do this with registrars, like godaddy all the time. Try reading the FAQs at the registrar.
Neither of these approaches (using your own server, or using the nameservers provided by your registrar) is likely to give you a level of service conmensurate with your server choice.
Go with a third-party DNS provider. They are easy to find with a search engine or directory.
There are only 3-4 companies in the very top tier. This is probably overboard unless you have a MAJOR corporate or e-commerce site. They are relatively expensive, but provide absolutely top-notch service. They have some special tricks up their sleeves. They have multiple servers on each IP address, which provides "invisible" mirroring. Besides the additional redundancy, a nice additional feature of this is that DNS requests are answered by the NEAREST DNS server. This technology is called IP Anycast. You will see these 3-4 companies being used by many of the top names.
There is a second tier of companies that provide service at a pretty reasonable fee of typically just a few dollars a year per domain. You can get packages for multiple domains for low single-digit dollars per year. Some of these companies offer the same IP Anycast technology as the first tier, but perhaps not with as many redundant servers, but still providing servers on 3 continents. (Typically U.S., Europe, and Asia.)
It should be pretty easy to pick one. Find the top 15 DNS hosting companies, and then pick one, on a similar basis to how you picked your hosting company.
I am getting the drift of what you are inferring, more hints would be appreciated. This particular network is 100 sites and cheapest DNS I have seen so far is cost prohibitive.
Now you see a ZONE File editor.
5. Print the page with the current settings (you may need to reset data back to it's oroginal settings at a later date)
6. Under the "A Host" section, look for "@ XXX.XXX.XXX.XXX 3600 edit delete" (Where XXX.XXX.XXX.XXX is an IP Address), select "edit"
The current IP Address listed is the IP address of the web server that users will see content from if they type in www.yourdomainname.com.
7. On the "A Host Record" page, change the IP Address in the "Enter Points To IP Address" section to the IP Address of your dedicated web server.
8. Select "Continue"
9. On next page, select "Update"
After about an hour, the IP Address should resolve to your web server's IP Address.
Try using the tools at dnsstuff to check the DNS entry for the domain's "A Record" to verify that the change has taken place.
Hope this helps.
[edited by: Webwork at 2:40 pm (utc) on Feb. 21, 2006]
[edit reason] My bad. No actual edit. [/edit]
My instructions were tailored to using the registrars DNS, which may or may not meet your specific performance requirements.
Also, the registrar's DNS servers might block requests from certain countries that you may not want blocked.
As with most things, you get what you pay for. If you are expecting 100,000s or 1,000,000s of visitors per day, then you will likely want to outsource to a mid-level DNS provider. If you are only getting 20,000 to 50,000 visitors per day, then the mid-tier or the registrar might meet your needs. If you are below 20,000 visitors per day, then you might want to just use a registrar.
You could start with the registrar and move up to a mid-tier provider as your traffic/revenue increases. If you can afford it, a mid-tier DNS provider with geographic redundancy is a good way to go.
This particular network is 100 sites and cheapest DNS I have seen so far is cost prohibitive.
You should be able to do this for a little over $100/year for 100 domains. Sticky me if you are having trouble finding a provider.
Considering that your registration cost has to be at least $600/year, this shouldn't be cost-prohibitive.
With 100 domains, managing this with your registrar's DNS could be time-consuming. Depends on your registrar.
Third-parties typically provide the ability to set-up templates that you can apply to multiple domains, so managing 100 domains is a snap.
