KNOWNHOST WIKI

User Tools

Site Tools


dns:creating-nameservers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dns:creating-nameservers [2016/03/21 23:51]
mscherf draft progress - Still in Progress!
dns:creating-nameservers [2016/03/22 18:46]
mscherf removed Plesk and Hostgator
Line 44: Line 44:
  
 ==== DirectAdmin ==== ==== DirectAdmin ====
- 
-Coming soon! ((waiting for example environment,​ to get the exact names of the options correct)) 
- 
-==== Plesk ==== 
  
 Coming soon! ((waiting for example environment,​ to get the exact names of the options correct)) Coming soon! ((waiting for example environment,​ to get the exact names of the options correct))
Line 61: Line 57:
   * [[http://​www.enom.com/​kb/​kb/​kb_0307_modify-delete-nameservers.htm|Enom]]   * [[http://​www.enom.com/​kb/​kb/​kb_0307_modify-delete-nameservers.htm|Enom]]
   * [[https://​www.godaddy.com/​help/​creating-your-own-nameserver-registering-your-own-domain-hosts-12320|GoDaddy]]   * [[https://​www.godaddy.com/​help/​creating-your-own-nameserver-registering-your-own-domain-hosts-12320|GoDaddy]]
-  * [[http://​support.hostgator.com/​articles/​hosting-guide/​lets-get-started/​domain-names-buy-sell-manage/​how-do-i-know-if-my-domain-is-registered-with-launchpad-or-hostgatorenom|HostGator]] via [[http://​support.hostgator.com/​articles/​hosting-guide/​lets-get-started/​dns-name-servers/​setting-up-private-name-servers-with-hostgatorenom|eNom]] or [[http://​support.hostgator.com/​articles/​hosting-guide/​lets-get-started/​dns-name-servers/​setting-up-private-dns-with-launchpad-domains|LaunchPad]] 
   * [[https://​www.namecheap.com/​support/​knowledgebase/​article.aspx/​768/​10/​how-do-i-register-personal-nameservers-for-my-domain|NameCheap]]   * [[https://​www.namecheap.com/​support/​knowledgebase/​article.aspx/​768/​10/​how-do-i-register-personal-nameservers-for-my-domain|NameCheap]]
   * [[https://​www.name.com/​support/​articles/​205934457-Custom-Name-Servers|Name.Com]]   * [[https://​www.name.com/​support/​articles/​205934457-Custom-Name-Servers|Name.Com]]
Line 69: Line 64:
 {{howhard>​3}} {{howhard>​3}}
  
-Next, it is a good idea to double-check that the dns zone for the domain in the server has the right NS records and SOA records to use the newly-created nameservers. This step can also be done at the same time or right after "A records in server"​.+Next, it is a good idea to double-check that the dns zone for the domain in the server has the right NS records and SOA records to use the newly-created nameservers. This step can also be done at the same time or right after "A records in server"​. ​Since this step is done within the server, we can do it for you if you open a [[https://​support.knownhost.com|Support Ticket]]. If you prefer to do this part yourself, the instructions are below:
  
 ==== cPanel ==== ==== cPanel ====
Line 82: Line 77:
  
 ==== DirectAdmin ==== ==== DirectAdmin ====
- 
-Coming soon! ((waiting for example environment,​ to get the exact names of the options correct)) 
- 
-==== Plesk ==== 
  
 Coming soon! ((waiting for example environment,​ to get the exact names of the options correct)) Coming soon! ((waiting for example environment,​ to get the exact names of the options correct))
  
 ===== NS records at Registrar ===== ===== NS records at Registrar =====
 +
 +{{howhard>​1}}
  
 Once you have checked that the domain'​s dns zone is ready to accept queries for the domain, the NS records can then be changed at the registrar as well, so that the new settings will begin propagation. As with creating the A records, this step will need to be done by you or the domain owner, and if you need help you will need to contact the registrar for assistance. But here are some guides for some of the more common registrars we see. Once you have checked that the domain'​s dns zone is ready to accept queries for the domain, the NS records can then be changed at the registrar as well, so that the new settings will begin propagation. As with creating the A records, this step will need to be done by you or the domain owner, and if you need help you will need to contact the registrar for assistance. But here are some guides for some of the more common registrars we see.
  
-  * Enom +  * [[http://​www.enom.com/​kb/​kb/​kb_0086_how-to-change-dns.htm|Enom]] 
-  * GoDaddy +  * [[https://​www.godaddy.com/​help/​set-custom-nameservers-for-domains-registered-with-us-12317|GoDaddy]] 
-  * HostGator +  * [[https://​www.namecheap.com/​support/​knowledgebase/​article.aspx/​767/​10/​how-can-i-change-the-nameservers-for-my-domain|NameCheap]] 
-  * NameCheap +  * [[https://​www.name.com/​support/​articles/​205934547-Changing-Your-Name-Servers|Name.Com]]
-  * Name.Com+
  
 ===== Other Domains to use these Nameservers ===== ===== Other Domains to use these Nameservers =====
  
-If you also want any other domains to use these new nameservers as well, you would repeate ​steps "NS records in the Server"​ and "NS records at Registrar"​ for each domain you would like using these new nameservers. You do not need to repeat steps "A records in server"​ and "A records at Registrar"​ since those steps need to be done once to create the nameservers,​ but steps "NS records in the Server"​ and "NS records at Registrar"​ need to be done for each domain.+If you also want any other domains to use these new nameservers as well, you would repeat ​steps "NS records in the Server"​ and "NS records at Registrar"​ for each domain you would like using these new nameservers. You do not need to repeat steps "A records in server"​ and "A records at Registrar"​ since those steps need to be done once to create the nameservers,​ but steps "NS records in the Server"​ and "NS records at Registrar"​ need to be done for each domain
 + 
 +===== A Note About Propagation ===== 
 + 
 +When DNS changes are made, they are never going to be completely instant across the whole internet. The reason for this is that most resolvers((the servers that answer dns queries)) will cache the results of the queries. Theoretically,​ the TTL((Time To Live)) of each record should determine how long it is kept in cache in a given resolver, so the propagation can sometimes be sped up considerably by first reducing the TTL values (and allowing the new TTL values to propagate) before making any of the other changes (and then changing the TTLs back to normal values after the new information finishes propagating). But some resolvers ignore TTL values completely, so some corners of the internet might still not see the new information for a couple days. Also some resolvers might query other secondary resolvers, rather than directly querying the authoritative nameservers,​ which further delays propagation. This is why we often warn that although dns propagation usually completes in 24-48 hours, it can sometimes take up to 72 hours. 
 + 
 +In case you are interested, you can learn more about DNS propagation [[https://​en.wikipedia.org/​wiki/​Domain_Name_System#​Record_caching|here]]. 
 + 
 +You can get an approximation of how a given dns record is propagation using tools such as [[https://​www.whatsmydns.net/​|whatsmydns.net DNS Propagation Checker]]. This will not give you a complete picture due to its small sample size, but can give you a vague idea of where in the propagation process the recent changes are.
  
-<WRAP todo>​Placeholder:​ Still in Progress!</​WRAP>​ 
dns/creating-nameservers.txt · Last modified: 2016/03/22 18:46 by mscherf