Your problem is that you originally gave the hosts unusual names. kb3vwg.ampr.org and www.kb3vwg.ampr.org are okay, but you should not have used names like kb3vwg-001.ampr.org but instead should have used something like 001.kb3vwg.ampr.org or sys001.kb3vwg.ampr.org. That way, all your names neatly go into a tree that they now call a "subnet". I claimed my "pe1chl" subnet and now I can edit all names of the form pe1chl.ampr.org and host.pe1chl.ampr.org. (even though they are not at all a single IP subnet, they are named that way in the portal)
What is so unfortunate about the new situation is that there is no quick way to fix this. Before, someone who was trusted (like all registered IP coordinators, which I think you were one yourself) could just edit these records and make them match the requirements. Now, we need to jump through those "ticket" hoops, wait a long time for the ticket to be assigned, and then it is usually answered with "can't do that", "can't honor that request", "you need to do that in a different way", etc. A lot of personal time (both on the requester and ARDC side) is now wasted on handling administrative overhead, and still we are getting nowhere.
Indeed, it is more what you expect from a utility corporation than from a service ran by fellow amateurs, enthusiasts in the same hobby.
Rob
On 2024-05-15 10:16, lleachii--- via 44net wrote:
I would use the term "corporate" maybe?
More so on topic - someone did respond about the tickets. Since they didn't really address who they were and their position or authority, I won't mention the call/name. They also explained why they wouldn't process 20 remaining tickets.