3 ms·
This could be Nominet fault. Years ago as a registar had to send PGP signed emails to some Nominet automated address to make changes or register UK domains, it
by sitepodmatt 9y ago
This could be Nominet fault. Years ago as a registar had to send PGP signed emails to some Nominet automated address to make changes or register UK domains, it was clumsy, slow and you had to maintain the state yourside. Nominet then got some independence, a CTO, a sales/business dev department dedicated basically to domain snippers, and Oracle got a ton loads of money (it was one of giant Sun mainframes if I recommend correctly) and it was still a PITA. This was 15 years ago apparently it is still a train wreck. When you start making decisions on the golf course its very difficult to recover
- 0x0 9y agoThis is interesting. I know that some TLDs have very antiquated, 100% manual management of registrations and transfers, although I wasn't aware that .uk was one of them. So to be fair it might not be eNoms fault. The timeline with over 122 days before any useful action was taken, coupled with the apparent misunderstanding and LOCKING of the reporter's account, still reflects extremely poorly on eNom's support department.
- sitepodmatt 9y agoInternic used to send you a paper invoice a few months after registering a .net, you then had to tear it off and send a us$70 check to them - and this applied if you were in the UK too, that all changed with joker.com iirc. Nominet system was just poorly engineered, slow (occasionally took hours) and damn right nasty to use in an end to end automated fashion - parsing emails for clues of errors etc.. The Oracle upgrade was just OTT for a system managing maybe 5m domains at the time (not an NS provider, although maybe they managed a root), the early 2000 version of big data, big money and loads of golf (Im guessing on the golf).