In Progress CPANEL-36573 - Adding and editing multiple records in DNS Zone Manager

[jndawson]

Turns out the issue is even worse than we thought. We can't edit ANY zones that start with a numeral; the latest 'upgrade' removed them from the /etc/userdomains file, so you have to add them back manually. cPanel tech opened Case CPANEL-36573.

Apparently you can add your name to be informed when there's a fix:

https://support.cpanel.net/hc/en-us...stem-does-not-have-a-domain-named-domain-tld-

 

[cPRex]

@jndawson - thanks for bringing this to our attention. The issue here isn't specifically with zones that start with a number, but zones owned by the system user get removed from /etc/userdomains so they don't show up properly in the interface.

If you are signed in to our ticket system you can "follow" that case for an update, but I'll be sure to keep this thread updated as well.

 

[jndawson]

@jndawson - thanks for bringing this to our attention. The issue here isn't specifically with zones that start with a number, but zones owned by the system user get removed from /etc/userdomains so they don't show up properly in the interface.

The subject numeral-starting domain is assigned to a user account - not the system.
The issue is making DNS user-based as opposed to domain-based (don't get me started on DKIM records). Besides the rDNS records, we have a bunch of zones that were never associated with a user account, so we can't edit those, either. Also, what's the point of having DNS clustering if you can't manage your DNS from one box?

If you are signed in to our ticket system you can "follow" that case for an update, but I'll be sure to keep this thread updated as well.

The update is to manually add the zone to /etc/userdomains.

 

[jndawson]

Manually adding the rDNS zones works. We'll see what happens after midnights run tonight to be sure /etc/userdomains doesn't get groomed.

It's ridiculous to have to do this, especially when we use DNS clustering and generally manage all zones from the same box, including rDNS with IP subnets spread across several servers.

Does anybody have any idea why DNS has shifted to user-based DNS management rather than domain-based DNS management? We have a bunch of domains that are not associated with hosting accounts and it makes no sense to have to assign them to a user that doesn't exist.

 

[cPRex]

As far as the "why" I can say it's not really the intended behavior, which is why we have that case opened to get things fixed. Following along with the page you linked is the best way to get updates as we do update those articles as our team resolves issues.

 

[jndawson]

The zones we added to /etc/userdomains disappeared after midnight crons ran. So, we're back to not being able to edit rDNS zones nor any other zone that is not associated with a user account.
Somebody needs to seriously review the entire zone manager project as it is breaking things.

 

[jndawson]

As far as the "why" I can say it's not really the intended behavior, which is why we have that case opened to get things fixed. Following along with the page you linked is the best way to get updates as we do update those articles as our team resolves issues.

There was a link within the page that supposedly provided more info, but it was pointing to info on the DNS Zone Editor and has been removed.

 

[cPRex]

Thanks for the update - I've added the removal issue to the case notes.

 

[jndawson]

Based on testing on our box, a temporary, jury-rigged, manual work-around works, fully outlined here:

cPanel

support.cpanel.net

Still no word on whether DNS will continue to be hamstrung by using a user-based management system rather than a domain-based system. At the very least, the old editor needs to be re-instituted until it's fixed.

 

[cPRex]

We've updated the workaround so that will no longer be wiped, which has also been pushed to that support page you linked.

 

[jndawson]

We've updated the workaround so that will no longer be wiped, which has also been pushed to that support page you linked.

Great.
Can somebody re-install the Zone Editor until whoever it is figures out how to fix the totally non-standard user-based management system?

 

[cPRex]

There is no way to install the older Zone Editor at this time.

 

[PeteS]

EDZ is still in WHM, but with the updated notice "We plan to remove the “Edit DNS Zone” interface from WHM in version 96."

Don't do it! Don't remove EDZ from WHM (at all IMO), at least until DZM actually helps us rather than hurts. Why NOT just leave both in WHM?

 

[jndawson]

EDZ is still in WHM, but with the updated notice "We plan to remove the “Edit DNS Zone” interface from WHM in version 96."

Don't do it! Don't remove EDZ from WHM (at all IMO), at least until DZM actually helps us rather than hurts. Why NOT just leave both in WHM?

It's already been removed from v.96. If you don't have a pre-96 WHM box running, you're out of luck, apparently.

 

[PeteS]

It's already been removed from v.96. If you don't have a pre-96 WHM box running, you're out of luck, apparently.

I'm on RELEASE, not CURRENT, so that's why.

@cPRex ...and I just moved to LTS! Rex, what's the deal? This is crap... apparently it's not ready, doesn't do what is needed, nobody wants it, and here you go sneaking/cramming it down our throats! Who's with me?!

 

[cPRex]

@PeteS - besides issue CPANEL-36573 that is being actively worked on, are you seeing other issues with that interface?

 

[PeteS]

@PeteS - besides issue CPANEL-36573 that is being actively worked on, are you seeing other issues with that interface?

Yes, the one that started this whole push-back. The inability to add or edit multiple records in one go! Imagine needing to add (or edit) a series of records such as for an external MX (just one of many possible scenarios). EDZ allows you to simply type in additions, or edits, or even both at once and hit enter, and boom, you're done. Having to click all over the place to do the same thing is laborious.

And I'm wondering what is it that makes cPanel even want to make this change? What's in it for you? What's in it for us? Why not just leave both? It there some problem with having EDZ in WHM, or is it blocking some other development?

Thanks.

 

[cPRex]

Leaving both is rarely an option - while it sounds easy to just leave something alone, it doubles the amount of development work and upkeep that needs to happen behind the scenes.

I believe the "why" is to make it more like the version available inside cPanel, and ease the development process from having to maintain multiple versions. I totally get the pain point of the multi-editing, and that will get resolved as part of this case.

 

[PeteS]

Leaving both is rarely an option - while it sounds easy to just leave something alone, it doubles the amount of development work and upkeep that needs to happen behind the scenes.

Totally get that, and agree. I was just frustrated.

I believe the "why" is to make it more like the version available inside cPanel, and ease the development process from having to maintain multiple versions. I totally get the pain point of the multi-editing, and that will get resolved as part of this case.

That makes sense. I am really pleased to hear that the multi-edit/add issue is being addressed! I didn't realize it was part of the case (36573?).

Just curious, is DZM in v96 the same as in v94?

Thanks

 

[cPRex]

Ah, I checked and that's not covered under the same case number. Multi-editing is case CPANEL-33635 :D but it's definitely on the radar.