i have to admit, i have no idea what i'm doing on this one. how the heck to i set up DNS zones?
1. do i have to have the actual nameservers that i want to use for the server placed in the master DNS zone template, or do i leave the template blank with all the <domain> and <ip> stuff?
2. if i have personal nameservers registered... how do i set it up to use those nameservers for the whole server? as in, do i actually have to enter those nameservers somewhere in the DNS zone?
this is what my current master DNS zones for the server looks like:
Host Record type Value
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<domain>. NS ns.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns.<domain>. A <ip>
webmail.<domain>. A <ip>
anyone answering, just assume that i'm a complete idiot and talk very slowly.. hehe.
Vagrant Web Hosting - U.S. / CANADA
Website Hosting - Website Development - Content Management NEW: Windows Hosting w/ ASP.NET
First, get rid of the A record for ns.domain.com and the NS record for ns.domain.com -- I still do not understand to this day why Plesk does that, hardly anyone does that.
For your master DNS template, add 2 NS records. ns1.whatever.com and ns2.whatever.com -- those will be your nameservers for every domain. Now, if you're using your own, go into that domain's DNS and add 2 A records. Point NS1.WHATEVER.COM to the IP it is, and then NS2.WHATEVER.COM to the IP it is. After that, login to ssh, and do
And add the following
domain domain.com (Make the domain the domain of the one you're using for the nameservers)
You don't have to add both if both IPs are on the same box, you can just add one. However, if they are on 2 different servers, then there you go.
Originally posted by Locke First, get rid of the A record for ns.domain.com and the NS record for ns.domain.com -- I still do not understand to this day why Plesk does that, hardly anyone does that
Because, unlike Cpanel, domains in an account do not inherit the primary domain's DNS record. So when a reseller adds a domain, they don't have to touch the dns file as it will work fine just the way it is with the A record bound to NS record. Of course alot of resellers do like to brand the dns as well and will edit the dns file but not all understand it and manually editting the dns appears to cause more problems than its worth. We leave the dns like that on our reseller servers but on the shared servers we edit the default zone and put in our anonymous nameservers.
██ Laurence Flynn @ atOmicVPS LTD ██ Linux & Windows Cloud Hosting Solutions Powered by OnApp
██ Fully Managed [Shared] ► [Reseller] ► [Cloud VPS] ► [Dedicated]
██ Featuring the atOmicSTACK™ ● Speed ● Performance ● Reliability