How did this happen?

[Systreg]

Sign up to Nominet using the same email address as you do on DM, I'm sure it will be there. Not that it matters, Nominet need to investigate how this happened.

To do that I'd have to set up that bloody 2FA again for the new account, and I'm not prepared to do that, as the 2FA fecked up when I tried doing it for my main account, it wouldn't accept the phone number or something, so had to do it again and then it said the number already in use, so I had to use the Mrs' phone second time.

I then got locked out of my account and had to send of ID to get back in to my account, so I ain't going through all that 2FA crap again.

I've sent a support message to Domain Monster telling them that the domain is nothing to do with me, and it needs to be changed back to Lee's name or changed back to his tag, Lee is aware of this as we had a chat earlier.

 

[ian]

I've sent a support message to Domain Monster telling them that the domain is nothing to do with me, and it needs to be changed back to Lee's name or changed back to his tag, Lee is aware of this as we had a chat earlier.

Morally the right thing to do of course, but don't act too quickly, it is possible (though I suspect highly unlikely) that Domainmonster did actually register the domain first and due to a glitch, didn't correct straight away. Nominet will be able to confirm this. You might by rights be the correct owner...though again, seems unlikely.

So from your conversation with Lee, did he move the domain to Domainmonster, or did it just move itself?

 

[Systreg]

@ian, I asked Nominet for a timeline of what happened since the catch, they replied to me today and said:

The domain was previously registered with the registrar DROPCAUGHT-RO, however they then moved the domain name over to the MONSTER registrar tag on the same day.

Monster then updated the registrant details to your details and this can now be seen on the Whois directory.

They then suggest contacting Domain Monster support, which I'd already done, and I sent a follow up DM to them on Twitter 15 minutes ago with all of the details again.

 

[DaveP]

Why would a tag owner move a newly caught domain name to Domain Monster? It makes no sense whatsoever, and I don't think Lee Owen would've done this.

Very interesting nonetheless, would be interesting to know what happened so it doesn't happen to others in the future. Lee is lucky it was sent across to Kevin, it could've been someone else who wouldn't give up the domain so readily.

 

[Systreg]

I emailed Nominet again asking why they can't do a tag change from their end to rectify it, they replied:

As it was DomainMonster that made the change to the Registrant (as an Accredited Registrar), we need it to be them that make the changes back.

DomainMonster have responded to a request for some clarification from us, and it is my understanding that they are reverting that change. It appears to have been a case where there was a presumption that the domain name had been caught for you when the domain name appeared on their Tag.

Glad to hear they will be reverting back to the original registrant, but I think that's a silly excuse from Domain Monster in presuming they caught it, can't their system tell the difference. If it was transferred in to them, that would suggest it wasn't them that caught it

 

[ian]

But doesn't that imply that Lee transferred it from his tag to Domainmonster?

 

[Systreg]

Yes, as above, I posted that Nominet confirmed it was caught and transferred to Domain Monster, they then presumed they caught it for me and added my registrant details to it.

 

[RobM]

Well it's possible that this happened:

There is a backorder at domainmonster.
It is caught by dropcaught.ro. The person who caught it then transfers it in to domainmonster. I guess Lee *did* initiate the transfer expecting it to go into his account there.
However domainmonster later check through and see the tag is theirs.
They therefore automate changing the details to the person who backordered at domainmonster - ie Kevin.
It seems to me a combination of two clients having accounts at the same registrar - one placing the backorder - and the other transferring in the same day as the drop.

 

[DaveP]

It is caught by dropcaught.ro. The person who caught it then transfers it in to domainmonster. I guess Lee *did* initiate the transfer expecting it to go into his account there.

He already mentioned that he didn't release to Domain Monster. I mean why would he move any domains there when he has his own tag? I don't see them currently running any renewal promotions?

 

[Systreg]

Yeah, pretty much how @RobM described, athough I don't know how the Domain Monster system can't tell the difference between them making a catch, or someone transferring a domain in and them thinking they caught it.

@DaveP, it's not mentioned anywhere in this topic that Lee said he hadn't released it to Domain Monster, you must have read his tweet wrong? In that, he said he never released it back to the pool, meaning it wasn't deleted and then caught by Domain Monster.

 

[DaveP]

Yeah, pretty much how @DaveP, it's not mentioned anywhere in this topic that Lee said he hadn't released it to Domain Monster, you must have read his tweet wrong? In that, he said he never released it back to the pool, meaning it wasn't deleted and then caught by Domain Monster.[/USER]

It was his tweet I was referring to, but you're right I did misread it.

 

[Lovekraft]

He already mentioned that he didn't release to Domain Monster. I mean why would he move any domains there when he has his own tag? I don't see them currently running any renewal promotions?

My guess is he might have moved it to Domainmonster for some simple DNS provision.

 

[aZooZa]

Owned by MT now - looks like all resolved.

 

[newguy]

All's well that ends well.

 

[Systreg]

Yeah, all done and dusted, next time I'm keeping it