How to stop the nameservers entered in WHM leaking?

harmonypersechino5348

• February 10, 2021 20:09

I am having an issue adding a domain to my server. Why is it that when you run a nameserver check on sites like https://i.gyazo.com/f20b34205dd3a9d4b6be88fd73b1bf78.png

• 

  andrew.n

  • February 11, 2021 07:03

  You have to register your nameservers as "private nameservers" at your domain registrar...probably this is what it's checking. So you you use ns1.test.com and ns2.test.com then you have to visit the domain registrar of test.com and register ns1 and ns2 as private nameservers with their respective IP addresses.

  0
• 

  kodeslogic

  • February 11, 2021 09:17

  Yes, you'll have to create child nameservers ns1. xyz.com and ns2. xyz.com at your domain registrar end.

  0
• 

  harmonypersechino5348

  • February 11, 2021 12:37

  These are registered and working but the issue seems to be cPanel creates a ns record for every nameserver listed in that " WHM > Basic Webhost Manger > Nameservers" list. This is resolved now thanks.

  0
• 

  cPRex Jurassic Moderator

  • February 11, 2021 15:47

  @harmonypersechino5348 - you are seeing the correct behavior. The nameserver details that are entered into the WHM >> Basic WebHost Manager page are the "default" nameservers on the system, so they will get added to the DNS zone for every domain that gets created on the machine.

  0
• 

  harmonypersechino5348

  • February 11, 2021 15:49

  @harmonypersechino5348 - you are seeing the correct behavior. The nameserver details that are entered into the WHM >> Basic WebHost Manager page are the "default" nameservers on the system, so they will get added to the DNS zone for every domain that gets created on the machine.

  
  Yes it was my misunderstanding on how it works. I am unable to remove all of them due to the requirement for SOA records

  0

Please sign in to leave a comment.