Use the nameservers specified at the Domain’s Registrar

Planky

• April 12, 2015 22:50

When creating a new account, you have the following option: "Use the nameservers specified at the Domain"s Registrar. (Ignore locally specified nameservers.)" Existing accounts do not have this option available (under Modify an Account); how can I change this?

• 

  cPanelMichael

  • April 13, 2015 18:34

  Hello, You can use the "Edit DNS Zone" option in Web Host Manager to change the name servers for existing domain names in their DNS Zones. Note that you should also change the name servers at the domain registrar. Thank you.

  0
• 

  oah

  • March 25, 2020 09:47

  Hi @cPanelMichael I am using cloudflare for my DNS records, does it matter if I check the "Use the nameservers specified at the Domain"s Registrar. (Ignore locally specified nameservers.) " option, since I am already handling the DNS stuff at cloudflare? What is your outtake on that? Thx.

  0
• 

  yesgeek

  • April 09, 2021 14:21

  Hi @cPanelMichael I am using cloudflare for my DNS records, does it matter if I check the "Use the nameservers specified at the Domain"s Registrar. (Ignore locally specified nameservers.) " option, since I am already handling the DNS stuff at cloudflare? What is your outtake on that? Thx.

  
  I'm curious about this also if it effects AutoSSL validation when using Cloudflare. For now I have to disable cloudlfare protection then run autossl and then enable it again in order to get a full SSL encryption. I was wondering if adding cloudlfare name servers in WHM would avoid me having to remove the cloudflare protection.

  0
• 

  cPDavidL

  • April 09, 2021 19:19

  Hi @cPanelMichael I am using cloudflare for my DNS records, does it matter if I check the "Use the nameservers specified at the Domain"s Registrar. (Ignore locally specified nameservers.) " option, since I am already handling the DNS stuff at cloudflare? What is your outtake on that? Thx.

  
  The option to use nameservers specified at the registrar, is specific to the account creation process. It only changes the NS records created locally to use those returned by public whois records, instead of the inherited nameservers from the reseller or root. Ultimately, if the domain owner continues to use 3rd party nameservers, it does not matter at all because public-facing DNS will not change.

  I'm curious about this also if it effects AutoSSL validation when using Cloudflare. For now I have to disable cloudlfare protection then run autossl and then enable it again in order to get a full SSL encryption. I was wondering if adding cloudlfare name servers in WHM would avoid me having to remove the cloudflare protection.

  
  My understanding is that it would not. The issue with cloudflare protection is that it interferes with the http method within the domain control validation process, more specifically, the Sectigo or LetsEncrypt user-agents used in the DCV request.

  0

Please sign in to leave a comment.