Unable to update ttl
One of our clients was setting up a new MX zone for a domain they're managing, and they noticed the TTL box was grayed out. It was set to 14400, and they were unable to change it. I tested it myself, and I couldn't edit it either as root in WHM. I even tried changing the server default from 14400 to 3600. I went to the account and tried setting up a new record, and it was grayed out and set to 14400 instead of the new default. This happens for all record types as far as I can tell (I only tried a few, but it's unlikely I accidentally picked the three records that have an issue - more likely system-wide).
I'm not sure exactly when this started, but I was able to change TTL as of 2-3 weeks ago. Any thoughts on why this might be, and if it's a known issue, is there a fix coming in a future release?
-
I was looking at that thread, and I thought the same thing. But I wasn't certain, since there wasn't a mention of this specific issue. Also, it seems odd for a bug to set an input box to disabled. Do we know for sure that the two are related? 0 -
For the box itself being disabled, I'm not sure - it might be best to submit a ticket to our team so we could check out the individual machine in question. 0 -
Same problem here after 96.0.x update. Cannot edit any TTL values for MX records in cPanel Zone Editor nor in the WHM > DNS Functions > DNS Zone Manager This is creating an issue for custom / remote MX modifications. :( 0 -
Hello Metro2! Would you mind confirming the exact build of cPanel running on your server? You can verify this with the following command: /usr/local/cpanel/cpanel -V0 -
Hello Metro2! Would you mind confirming the exact build of cPanel running on your server? You can verify this with the following command:
/usr/local/cpanel/cpanel -V
Sorry, I should have mentioned 96.0.9 (I have WHM Update Preferences set to Release Tier on my servers) and run CloudLinux 6 ELS [~]# /usr/local/cpanel/cpanel -V 96.0 (build 9)0 -
Thank you for that clarification. I was reviewing the internal case that was filed on the issue, and it appears to be fixed as of build 10, which may explain why you are still experiencing the error. 11.96.0.10 is also our CURRENT tier. Could you try updating to build 10 to see if the issue persists? 0 -
@cPJustinD Thanks for the reply. I wish to keep my Update Preferences set to "Release" tier, and cPanel has recommended in the past not to switch from "Release" to "Current" and then back to "Release". I don't see any option to update to build 10. What am I overlooking? 0 -
My /etc/cpupdate.conf is currently: CPANEL=release RPMUP=daily SARULESUP=daily STAGING_DIR=/usr/local/cpanel UPDATES=daily And since my servers are in production on which I sell shared hosting, and considering that I've read in the past that switching between "Release" and "Current" can cause issues / requires adjustments to database prefixing (perhaps my info is outdated or doesn't apply to 11.96?) I would be very hesitant to mess with anything that could cause and interruption of service for my customers. So yes, it's probably best to wait until build 10 reaches RELEASE tier. 0
Please sign in to leave a comment.
Comments
10 comments