3 ms·

2 Days ago management of .io registry was transfered from Afilias to Donuts (Due to an acquisition). It is likely that during that window you registered the do

2 Days ago management of .io registry was transfered from Afilias to Donuts (Due to an acquisition). It is likely that during that window you registered the domain and they are now cleaning up the issue. It may be your registrar took your registration and then when they went to actually process it the registry was down, so someone else got it during that period. It could be other things, however, the bottom line is that the domain was probably never yours and there is really not much to do here. It's bad timing and bad handling of a process on your registrars end.

forty 5y ago
At least right now I control the domain. I think the registry messed up as they allowed my registration, not the registar. Thanks for the info on the migration, that could indeed explain this.
- funnyflamigo 5y ago
  If you have control of it you _might_ actually be the one that nabbed it, and somebody else complained they couldn't manage it. If this is the case, under no circumstance tell your registrar you're okay with losing it and dig your heels HARD. Either way you should get a cert for it with the longest expiration you can ASAP while you control it ;)
  - robalfonso 5y ago
    I understand your sentiment here, but should the registry decide the domain is not theirs it will simply not be manageable from the registrar/buyer. All they do is update the management id to the new registrar and the registrant contact of the domain, no intervention is possible. I can tell you I’ve seen legal orders transferring a domain from one registrant to another, if the order has the registry named to take action, the domain kind of just goes poof, sure it’s in your system but you can’t do anything against it.
    - CogitoCogito 5y ago
      > I can tell you I’ve seen legal orders transferring a domain from one registrant to another, if the order has the registry named to take action, the domain kind of just goes poof, sure it’s in your system but you can’t do anything against it. Then maybe the original poster should demand such a legal order? I doubt there exists one now given it's only been a couple days.
      - robalfonso 5y ago
        In this context it was court orders, usually over an ownership dispute between corporations. The legal fees etc, make it unlikely to be worth the hassle.
        CogitoCogito 5y ago
        Yeah I can totally see that. I guess in this case the OP could try to stand strong and refuse to go along without any sort of court order, but even in that case it's not like the OP can stop the registry from going through with the change. So really if the registry decides to do it anyway, then I guess the OP could try to pursue legal options. I guess maybe the domain would be worth it.

forty 5y ago

At least right now I control the domain. I think the registry messed up as they allowed my registration, not the registar. Thanks for the info on the migration, that could indeed explain this.

funnyflamigo 5y ago
If you have control of it you _might_ actually be the one that nabbed it, and somebody else complained they couldn't manage it. If this is the case, under no circumstance tell your registrar you're okay with losing it and dig your heels HARD. Either way you should get a cert for it with the longest expiration you can ASAP while you control it ;)
- robalfonso 5y ago
  I understand your sentiment here, but should the registry decide the domain is not theirs it will simply not be manageable from the registrar/buyer. All they do is update the management id to the new registrar and the registrant contact of the domain, no intervention is possible. I can tell you I’ve seen legal orders transferring a domain from one registrant to another, if the order has the registry named to take action, the domain kind of just goes poof, sure it’s in your system but you can’t do anything against it.
  - CogitoCogito 5y ago
    > I can tell you I’ve seen legal orders transferring a domain from one registrant to another, if the order has the registry named to take action, the domain kind of just goes poof, sure it’s in your system but you can’t do anything against it. Then maybe the original poster should demand such a legal order? I doubt there exists one now given it's only been a couple days.
    - robalfonso 5y ago
      In this context it was court orders, usually over an ownership dispute between corporations. The legal fees etc, make it unlikely to be worth the hassle.
      - CogitoCogito 5y ago
        Yeah I can totally see that. I guess in this case the OP could try to stand strong and refuse to go along without any sort of court order, but even in that case it's not like the OP can stop the registry from going through with the change. So really if the registry decides to do it anyway, then I guess the OP could try to pursue legal options. I guess maybe the domain would be worth it.