Skip to main content

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

Comments

46 comments

  • cPanelLauren
    As far as automation goes you wouldn't use the UI to do this anyway you'd want to use the API so it wouldn't have any effect on how the UI behaves. Automation would utilize the WHMAPI1 functions here:
    0
  • cPanelLauren
    Hi @ITHKBO It looks like we're tracking concerns about this in CPANEL-33635 and I've added your forums thread here to the internal case. I've also had a discussion with one of the developers who works on the team that created this change and they should be responding here shortly as well with some more information. Thanks!
    0
  • cPanelDustin
    I'm currently working on a branch to revert the Edit DNS Zone UI in v90, but in the mean time, I would appreciate any feedback you could provide on the new UI in the study I'm conducting on it. Please be as detailed as you can be on how you use the functionality on a regular basis. You've been invited to participate in a short test.
    0
  • ITHKBO
    Hi @cPanelLauren Thank you very much for the API information you provided and relaying our information to the developers. Hi @cPanelDustin We have filled out the requested form. If any further information is needed please do let us know.
    0
  • jndawson
    [snip] Second and our most important question. How can we add or edit multiple DNS Zone records at the same time like in the previous version. (Edit DNS ZONE) Now admins have to fill in all values on one record than press "ADD RECORD" and than again on "+ ADD Record" and repeat this process instead of having 10 blank records to fill in as desired with different record types all with one handy save button. This new design makes it impossible to run any kind of automation nor work top to bottom with filling out records. Additionally this prevents us from editing multiple records which are to be updated at the same time. Like for example NS records. [snip]

    We are in the process of cleaning up over 900 zone records and having to edit every single record in a zone individually rather than edit all and then saving them all at once has dramatically extended labor costs. Additionally, changing the type of record (e.g., CNAME to A record) requires deleting the record completely, then creating a new record, again, increasing time and labor costs. Please revert back to 'Edit DNS Zone' as an option.
    0
  • PeteS
    While I do see your concerns about editing multiple RR's in the zone file through the UI I would suggest a feature request to improve this interface. Since it's still pretty new to WHM the team that worked on it is most likely still looking for feedback.

    Let's start with HOW did this even even make it off the drawing board? Seriously, I want to know the answer... How is this an improvement? I have always HATED the cPanel interface because it is SO SLOW when making one edit, let alone multiple edits. WHM was my happy place for DNS zone edits. Why would anyone think this is a good idea? Put a HOLD on removing it in v92, and keep EDZ in WHM until DZM works as it should! Or just scrap DZM entirely - who needs it? It's not a mere concern, it's a train wreck. @jndawson says "...cleaning up over 900 zone records..." That's a "quit my job" nightmare! A feature request?! You are taking away a surgeon's scalpel and giving us a plastic knife. There is not feature request that will fix this... unless it's an Edit All button that takes us to EDZ. :D Example from my last server migration: Amazon SES entries require FOUR entries. It's bad enough to have to go through each account to do that, but to have to make it four times as hard... #fail This. Is. Craziness. All theatrics aside: Please take the input here seriously and do something about this. It really is a no-brainer to see the problem for admins. I am serious also when I ask for a reason why this ever seemed like a good idea? -Pete
    0
  • cPanelDustin
    Just an update on this. We ended up putting a hold on removing EDZ in v92 as we haven't gotten the DZM quite where we want it. The plan is still to move to this soon, but we want to make sure it meets the needs of cPanel and WHM users alike before do.
    0
  • PeteS
    Just an update on this. We ended up putting a hold on removing EDZ in v92 as we haven't gotten the DZM quite where we want it. The plan is still to move to this soon, but we want to make sure it meets the needs of cPanel and WHM users alike before do.

    That is a good decision, and thank you! Please keep us posted on adding bulk update to DZM or other changes to it, and get feedback from admins before removing EDZ. -Pete
    0
  • jndawson
    Just an update on this. We ended up putting a hold on removing EDZ in v92 as we haven't gotten the DZM quite where we want it. The plan is still to move to this soon, but we want to make sure it meets the needs of cPanel and WHM users alike before do.

    Good. And when you DO implement it, be sure that it's capable of bulk changes, direct editing, and doesn't include more steps to make a change than necessary.
    0
  • PeteS
    "We"ve implemented the new "DNS Zone Manager" interface. Use this to edit your basic DNS zone records. We plan to remove the "Edit DNS Zone" interface from WHM in version 94." I really hope you DO NOT remove EDZ until AFTER you have DZM version that meets our needs. WHY would you want to make things harder for us? Don't do it! -Pete
    0
  • PeteS
    ***remove double post***
    0
  • cPRex Jurassic Moderator
    Currently the plan is to remove EDZ in 94, as version 92 shows this header at the top of the EDZ page: "We"ve implemented the new "
    0
  • PeteS
    Just an update on this. We ended up putting a hold on removing EDZ in v92 as we haven't gotten the DZM quite where we want it. The plan is still to move to this soon, but we want to make sure it meets the needs of cPanel and WHM users alike before do.

    Hi Dustin, In light of the above response from @cPRex can you tell us what changes have been made ("we haven't gotten the DZM quite where we want it" and "we want to make sure it meets the needs of cPanel and WHM users") since your last post? The single biggest complaint is about the need to bulk edit multiple entries ina zone in one go. Has that been addressed? I don't see that in v92's version, and I cannot see why you would want to remove the capability. -Pete
    0
  • cPanelDustin
    The EDZ won't be removed in v94. I've currently got a task to update that messaging. We made the decision to extend it one further release so that we can implement some specific improvements that make sense for WHM users. Multi-entry editing is a priority in that and EDZ will not be removed until DNS Zone Manager has at least that functionality. Basically, I'm not removing the old one until I'm satisfied that the new one meets the needs of Administrators.
    0
  • PeteS
    The EDZ won't be removed in v94. I've currently got a task to update that messaging. We made the decision to extend it one further release so that we can implement some specific improvements that make sense for WHM users. Multi-entry editing is a priority in that and EDZ will not be removed until DNS Zone Manager has at least that functionality. Basically, I'm not removing the old one until I'm satisfied that the new one meets the needs of Administrators.

    This makes me day! :) Thank you for that assurance about it not being remove prematurely, especially about multi-entry editing! It's really good to hear from those involved in development, and to know that we are heard. The result will be the best product possible. -Pete
    0
  • jndawson
    Firstly, I'm still not sure why the DNS editor needed improvement. Secondly, every 'upgrade' to the new DNS Zone manager cause more issues: ================================================================================================================ DNS Zone Manager DNS converts domain names into computer-readable IP addresses. Use this feature to manage DNS zones. For more information, read the API failure: (XID qp9y8v) This system does not have a domain named "240-16.117.251.198.in-addr.arpa". ================================================================================================================ How do we access our PTR records?
    0
  • cPDavidL
    How do we access our PTR records?

    General information about editing/updating PTR records, can be found here:
    0
  • jndawson
    General information about editing/updating PTR records, can be found here:
    0
  • jndawson
    We opened ticket #94315030 to address this.
    0
  • 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:
    0
  • cPRex Jurassic Moderator
    @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.
    0
  • 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? [quote]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.
    0
  • 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.
    0
  • cPRex Jurassic Moderator
    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.
    0
  • 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.
    0
  • 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.
    0
  • cPRex Jurassic Moderator
    Thanks for the update - I've added the removal issue to the case notes.
    0
  • jndawson
    Based on testing on our box, a temporary, jury-rigged, manual work-around works, fully outlined here:
    0
  • cPRex Jurassic Moderator
    We've updated the workaround so that will no longer be wiped, which has also been pushed to that support page you linked.
    0
  • 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?
    0

Please sign in to leave a comment.