Domain addon challenges due to nameservers (TXT Record verification possibility?)
-
For now we've added just a Predefined reply in our system to quickly answer clients with the way to verify the domain and add it to the account, that would be number 1 as we can't allow the parking of whatever domain to the server, with that said a TXT record verification would be a much better system yeah? 0 -
Generally, it's probably a good idea to use the nameservers of your hosting service rather than a 3rd party DNS server. While nobody can really stop someone from using a 3rd party DNS service, you have to understand that certain functions of cPanel (and any other control panels) really assumes that the domain name is using the nameserver stated for that web hosting service. If you use 3rd party DNS services, subdomains will not work properly. If anybody creates a subdomain, they will have to create the appropriate A record for the subdomain at their 3rd party DNS provider. The increase reliance on SPF and DKIM for email, means that you would have to insure that those records are applied correctly at the 3rd party DNS service so that DKIM verification for mail sent through the server is verified and that SPF records are correctly indicating what IP addresses are valid for sending mail from that domain. These are all things that get applied and work seamlessly if the domain is using the web hosting service's nameservers. Deviated outside of that expected setup means that you may face other consequences of that action. 0 -
@Steini Petur - you're always welcome to submit a feature request to the team! 0 -
Generally, it's probably a good idea to use the nameservers of your hosting service rather than a 3rd party DNS server. While nobody can really stop someone from using a 3rd party DNS service, you have to understand that certain functions of cPanel (and any other control panels) really assumes that the domain name is using the nameserver stated for that web hosting service. If you use 3rd party DNS services, subdomains will not work properly. If anybody creates a subdomain, they will have to create the appropriate A record for the subdomain at their 3rd party DNS provider. The increase reliance on SPF and DKIM for email, means that you would have to insure that those records are applied correctly at the 3rd party DNS service so that DKIM verification for mail sent through the server is verified and that SPF records are correctly indicating what IP addresses are valid for sending mail from that domain. These are all things that get applied and work seamlessly if the domain is using the web hosting service's nameservers. Deviated outside of that expected setup means that you may face other consequences of that action.
Those using 3rd party usually know the pitfalls of the subdomain requiring to be created in two places, people often do not wish to use your nameservers but the one provided by cloudflare and knowing the pitfalls, they should be able to somehow easily verify their domain ownership similar to any other known product like Squarespace etc, adding a TXT record to verify the ownership to add it. That's all.0 -
@Steini Petur - you're always welcome to submit a feature request to the team!
as TXT to your domain, then click and try again" you do it, the click runs this check, finds the TXT record, you are the owner, proceed.0 -
I reached out to our Domains team about that feature request, and they didn't say no! They also didn't say they were immediately going to start working on it either, but there's at least some hope. What is most likely to happen: at some point, we want to have a domain resolution testing tool built into the product, and this increased functionality for the remote domain configuration would get added to that. 0 -
I reached out to our Domains team about that feature request, and they didn't say no! They also didn't say they were immediately going to start working on it either, but there's at least some hope. What is most likely to happen: at some point, we want to have a domain resolution testing tool built into the product, and this increased functionality for the remote domain configuration would get added to that.
Thank you for the checkup cPRex, being a cPRex can have it's benefits =).. Anyway no one expected them to start working on it immediately but if it doesn't get lost in the shuffle, 4 years is a bit of a "dead discussion". As long as maybe it lights some fire under this idea that would be cool, I see no benefit of submitting it since he wrote about this like out of my own heart <3.0
Please sign in to leave a comment.
Comments
7 comments