SOLVED All reseller zones disappeared after transfer?

HELP! After using the Transfer Tool to migrate from server-A to server-B, when one of my reseller logs on their client's cPanel and click on Zone Editor, it's all empty. In the older server, they could manage their zone like MX record and SRV, TXT records.

In WHM tough, I can see all the zones, so I know they're on server-B alright, but they're completely "hidden" from each individual cPanel interface. How do I get them to show?

 

Anybody? Is there perhaps some sort of permission that would prevent zones from showing up in a reseller's customer's cPanel following a Transfer Tool migration from another server? They're showing up on server-A, why aren't they showing up on server-B? Same WHM version, all the exact same settings that I could change (I checked every single Tweak Settings line and they're exactly the same)

 

OKAY THANK YOU @Jcats . Indeed there's a checkmark missing next to "Zone Editor (AAAA, CAA, SRV, TXT)" so that's the solution. I liked your post, thanks again for this.

Now to cPanel: A suggestion would be that this features list would sync with the Transfer Tool like other settings. It would ease server migrations. Now I'll go over the whole server-A and server-B features list and compare to make sure everything 100% the same.

Thanks, you may close this thread.

 

@cPanelMichael Unfortunately, it's not on my server. FYI it's WHM 72.0 on both server-A and server-B.

Those are the only options available on mine and anyway all of them were checked when I migrated the server last night:

(lol, I see the picture when editing this post, but it doesn't appear on the public view... oh well, it's there:
- Removed -

 

Uhm OK, well I thought the IMAGE button was serving this purpose. Either way, I think I understand now what you tried to explain in your previous post about the PACKAGES. The way I thought it would have been is a list of ACL checkboxes (which I couldn't find as I posted in the screenshot that you removed) but now I understand that under the PACKAGES list, on the right hand, there's only a column that displays "default" since that's the only feature list collection I have on my server.

The problem is that all the packages I had on server-A always were on "default" and so, even tough I had checked all packages for the transfer, it imported them as the "default" feature list on server-B which is NOT equal to the "default" on server-A for some reason. Even when opening two browser tabs, I have trouble comparing the feature lists side by side, because it's not even listing the same ACL options even tough both servers are on WHM 72.0 which is quite puzzling!

The feature list is flawed by design. I would have expected the Transfer Tool to atomically segregate each ACL instead of just listing the name of the feature list ("default"). That "default" feature list NAME by itself doesn't explain to the Transfer Tool what ACL to set on the new server, so it's obvious now that it had to end up missing some. It's not even listing the same available ACL on both servers to begin with.

[server-A] >>>(import this package + set it to YOUR "default" feature list)>>> [server-B]
[server-B] >>>(uhm OK but shouldn't you explicitly state all its ACL's?)>>> [server-A]
[server-A] >>>(nah... yours are probably the same as mine anyway + I really don't care) >>> [server-B]
[server-B] >>>(OK whatever)>>> [server-A]

See what the design flaw is? Instead, it should be:

[server-A] >>>(import this feature list named "default" with these ACL's)>>>[server-B]
[server-B] >>>(uhm OK but I already have a "default" feature list here tough)>>> [server-A]
[server-A] >>>(right, well rename it because we need this to sync perfectly fine)>>>[server-B]
[server-B] >>>(oh yeah right, OK now that "default" feature list you wanted is named "default2" here)>>> [server-A]
[server-A] >>>(sure, as long as we're talking about the same ACL's)>>>[server-B]
[server-B] >>>(yeah yeah don't worry, they're safely stored in "default2" here)>>> [server-A]
[server-A] >>>(good, now import this package + set it to "default" feature list I sent earlier ("default2") on your end)>>>[server-B]

inb4 you reply to me that the "default" feature list shouldn't be different on two WHM 72.0 servers, well it is in my case and I don't even remember in 4 years having modified any of it. Even if I had, then if "default" is supposed to be the same on all servers having the same WHM version, then why is WHM allowing "default" to be modified? It should be locked and it should force the sysadmin to create another feature list profile to begin with.