I’ve yet to be told how Domain Jingles is involved in this, but

From what I understand, Domain Jingles is a Partner Registrar with eNom for acquiring dropping names. It appears that when I won the domain name from NameJet, the domain was registered in that credential by the eNom process that picks up names in the drop. Later on, the registry at Domain Jingles couldn’t communicate with eNom because a server had changed its IP address due to a subnet modification. For those people that have no idea what I just said - its basically “two computers couldn’t talk to each other”. Of course this doesn’t answer the question as to 1) why the name was removed from my account in the first instance and 2) why eNom support claimed it was no longer registered at eNom. When I contacted support to clarify the error message I was getting with the AuthInfo code (due to Domain Jingles changing their subnet), it seems that the support representative “marked” the domain name as transferred away in the eNom system which caused it to no longer appear in my account.

As you know, I tend to judge people on their auctions, not on their words; so if I was to summarize the experience I’d say that from a customer standpoint, eNom first level support were the main issue as they didn’t identify the problem from the outset. Once the matter was escalated, eNom management sorted it out. Their Tech Support Supervisor was in regular contact, as were senior management at Namejet and a former employee related to Domain Jingles (who just happens to read DomainerIncome).

From my point of view, the message from eNom has been clear - “If there are issues with a pending delete domain they should be reported. Should the problem remain the ticket should be escalated, and the issue will be worked until it is resolved.”

Thanks go to the staff and management at eNom and NameJet who sorted this out.

Tags: domain, enom, namejet, registrar