SOLVED How to stop the nameservers entered in WHM leaking?

harmonypersechino5348

Active Member
Dec 6, 2020
32
3
8
NA
cPanel Access Level
Website Owner
I am having an issue adding a domain to my server. Why is it that when you run a nameserver check on sites like NS Lookup - Lookup Nameserver of any Domain it's leaking whatever nameservers I put on WHM > Basic Webhost Manger > Nameservers (At bottom)?

Example my domain could be xyz.com pointed to ns10.xyz.com ns11.xyz.com however if in WHM I have ns1, ns2, n3, n4 it will show those 4 nameservers on sites like that. Is it because I am using Bind rather than PowerDNS? If so then how do I get .it domains to work with PowerDNS as they don't allow DNSSEC.

 
Last edited by a moderator:

andrew.n

Well-Known Member
Jun 9, 2020
633
183
43
EU
cPanel Access Level
Root Administrator
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.
 

harmonypersechino5348

Active Member
Dec 6, 2020
32
3
8
NA
cPanel Access Level
Website Owner
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.
 
Last edited:

harmonypersechino5348

Active Member
Dec 6, 2020
32
3
8
NA
cPanel Access Level
Website Owner
@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
 
  • Like
Reactions: cPRex