I'm a little puzzled about how the "DNS Node" server profile works I've been unable to find any documentation on it. From what I understand, this will provide a cpanel interface that only allows the end user to manage DNS zones? So I'm guessing the purpose is for clients who do not need hosting - they just want DNS. But what if they want to upgrade to a hosting plan later? Doesn't it completely cut off any sort of upgrade path? If I have a client that purchases a domain registration and wants DNS management, using a standalone "DNS Node" server for this would surely cause a problem if they wanted to upgrade to a hosting service. There would be no easy way to automate the switch to a completely different server. It seems unnecessarily complicated. I'm trying to understand what practical use we would get out of this and sadly it seems to me like a drop in functionality. With a "Standard Node" cpanel server, the client gets access to DNS functionality AND the ability to upgrade their package. With the DNS Node they can't go anywhere. You'd have to delete the account on that server and then set them up on a different one when they wanted to move up to a hosting product. That seems like a backwards step to me. On top of that, with the Standard Node, clients can add aliases in to one cpanel account, which allows them to manage the DNS Zones of all their domains in one place. It looks like the DNS Node appears to promote a separate cpanel login for every domain. That seems rather pointless. The only use I can see for this DNS node is for those providers that want to sell DNS services as a completely separate solution with no integration or ability to up-sell, or smoothly transition between products. The way I see it, clients want a smooth pathway that can go up and down between "Only DNS" "DNS and Email" "DNS and Web Hosting" "DNS and Email and Web Hosting". I understand the desire to put these products onto different servers, but there seems to be no connectivity or integration between them. I can see that cpanel are creating an Email Node - which goes some way to solving the Email storage issues - but right now it seems the roadmap is for the end user to have a separate DNS cpanel login, Email cpanel login and Hosting cpanel login. It doesn't sound very appealing at all. As a hosting provider, we want seamless integration between these products - not a complete disconnection and disassociation of them.
Please sign in to leave a comment.