Nameservers associated with a Zone are not consistent
Nameservers associated with a Zone are not consistent.
For example I have 2 sites both with nameservers set at cloudflare.
cPanel display this as expected in one Zone but not in the other
cPanel > Zone Editor > Manage Zone
Zone Records for “domain1.com”
Configured nameservers for this zone: ren.ns.cloudflare.com stimpy.ns.cloudflare.com
Zone Records for “domain2.com”
Configured nameservers for this zone: ns1.host.com ns2.host.com
My host refuses to assist or submit a query to cPanel. So I'm wondering why this happens, how can I update the display, or can I just remove this element of the display since my host says "it is just cosmetic" like they do for so many things, expecting me to remeber hudreds of settings to ignore.
-
Hey there! If these records are not showing up correctly that would indicate the NS record in the main DNS zone isn't set properly. This isn't something that an end user can adjust in cPanel, so the server admin would have to help reset that.
It's odd they wouldn't help with this as this would take only a few seconds to check for anyone with root access.
0 -
Hello cPRex
Thank you for chiming in.
I have root access to WHM, but don't know what proceedure to follow to correct the display of nameservers associated with a zone in a cPanel Zone.
The host support escalated to their "Advanced" support, only to say that
"This cPanel feature doesn't check for live data, only what is collected from server files on creation of the domain and will not update after that. It's cosmetic, nothing's broken, nothing to fix."
Is this false information? Which files does this feature check, is it /var/named/domain1.com.db ? Does it poll that file at all?0 -
If you have root access to WHM you should be able to check each zone file on the system to see what is configured for the nameservers there. I'd use the WHM >> DNS Zone Manager tool to check the NS records.
You can also check the default nameservers that will be used for future zone creation at the very bottom of WHM >> Basic WebHost Manager® Setup.
Although it may not be "broken" it still isn't "right" and I'd prefer to have it display correct information.
0 -
cPRex "Although it may not be "broken" it still isn't "right" and I'd prefer to have it display correct information."
Exactly my thoughts. From a user perspective it's like asking someone typing a text file to ignore the wrong text being displayed, because when it prints out the text will be correct. Unfriendly and counter-productive.
So, I do see the anomalous websites have the local nameservers in the WHM Zone Manager. I can of course update these manually, and when I do modify them to the CF nameservers, the change is reflected in the cPanel Zone Editor too.
However, is the typical server or WHM configuration supposed to update these nameserver strings automatically? If not, is this a possible feature request?
When setting up a new domain I always start with local nameservers, then migrate to cloudflare. I never manually modify the nameservers for a domain in WHM, so I'm wondering why some of the sites DO already have CF nameservers configured in the DNS files, but not others?
@... thank you for your input.0 -
Is this your process:
- Setup the DNS in cPanel
- Point the domains name servers to the cPanel name servers
- Add the domain at CloudFlare
- Point the domains name servers to CloudFlare
If that is what you do (and it sounds like it from the post above) then it's completely irrelevant what is in cPanel's DNS zone, but it's not the authoritative nameservers, CloudFlare is.
0 -
@ffeningol I half agree. Yes, that is the process I follow. Thereafter I mirror the DNS entries on both local and CloudFLare. The reason I do that is in some cases I've had to drop CF. Also not all domains on my local server are with CF, so when I look at my local servers Zone Editor view, it helps to see the correct nameservers displayed so that I don't have to dig about. So not completely irrevlevant, and if it was irrelevant perhaps it shouldn't be displayed in the Zone Editor at all, because looking at incorrect information slows the synapses.
0 -
timoto There simply is no way for cPanel to know that you updated the name servers at the registrar. You would have to manually update the name servers in cPanel/WHM after you updated them at the registrar. Similarly, cPanel/WHM would not know if you made any changes to the DNS zone at CloudFlare.
You may not like it, but you need to do a whois lookup first to see what name servers a domain is using and use that to figure out what DNS to check.
1 -
ffeingol
Really?
Hmm, so there's this thing called the internet where searching for a domain tells you the current nameservers, which cPanel could theoretically do via a linux command such as:
dig NS domain.com +short
or
nslookup -type=NS example.com
or
host -t ns example.com
So there's that for starters.
Again, if it is so difficult to display the correct information, why display it at all?0 -
I'm not sure we want to run a live DNS look up each time that page loads, as that could also break for other reasons than an incorrect configuration.
0 -
Not to mention that DNS like (CloudFlare) for example will let you do things that completely break RFC (like have the root of a domain not be an "A" record) that they handle in the background.
0 -
cPRex I'm wondering if there is a reason now to remove this information from the display? It is counter productive since there is no guarantee the information is valid.
ffeingol I don't think you can modify the nameservers in CloudFlare, or do anything non-standard regarding nameservers, it's fixed to their own nameservers which they assign at the time of assigning a site to their system.
0 -
At this point it would be best to see a ticket on this so we can see it in action. Would your provider be able to escalate that to us?
0 -
cPRex As mentioned, my host, Inmotion Hosting, is uninterested in lodging a ticket, citing that this is "cosmetic", which it is, but counter-productive make-up in my opinion.
So all I can do is make my suggestion here.
Thing is I think we have asserted that the current behviour is expected, so it's a product choice, do cPanel want to display invalid information, remove it, or make a feature change to display valid information.
0 -
I wouldn't say that invalid information is a widespread experience with this tool, which is I wanted to see this particular server.
0 -
Hi cPRex
I think it's easy to reproduce.
1. Registrar point domain to cPanel nameservers and IP.
2. cPanel create domain.
3. Registrar modify and point to other nameservers eg (CloudFlare) which has DNS pointing to the cPanel IP.
Does cPanel update the nameserver change? No. Therefore it displays legacy information in Zone Editor.
Please let me know if there is another way I can help you see what is happening.
0 -
Thanks for the specific reproduction steps. I believe this is getting handled as part of case CPANEL-56918 and I've linked this thread to the case internally, so if I hear any updates on my end I'll be sure to post!
0 -
Thank you cPRex.
Alex, I'm not sure what you mean by "newly created domains".
0 -
I'm 99% sure "Alex" is an AI bot of some sort.......but just waiting on some good evidence to ban that account.
0 -
@timoto, you mentioned me in your comment, but I didn't leave that AI-like message.
0 -
@... I'm not sure I've ever created a cPanel account without an associated FQDN.
But in theory I wouldn't expect any difference in behviour if cPanel is not checking for propagated updates from a registrar's configuration.
0
Please sign in to leave a comment.
Comments
20 comments