You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current solution adds deleteCandidate status to the domain registration that has passed its 'delete at' date. DeleteCandidate is set for random time for up to 24hrs. This is in conflict with domain regulations as the domain registration should not exist after delete at date has passed (no one owns that domain after that) and the deleteCandidate procedure just blocks the domain for being registered for a random period of time.
So the procedure should be as follows
domain is expired
after 15 days (configurable) domain is removed from zone
after another 30 days (configurable) domain registration is deleted (archived) and the domain is added to blocked/deleteCandidate list for a random period of time between current moment and end of the day (estonian time)
after the random period of time has passed the domain name is removed from blocked/deleteCandidate list and released for regular registration.
The text was updated successfully, but these errors were encountered:
Current solution adds deleteCandidate status to the domain registration that has passed its 'delete at' date. DeleteCandidate is set for random time for up to 24hrs. This is in conflict with domain regulations as the domain registration should not exist after delete at date has passed (no one owns that domain after that) and the deleteCandidate procedure just blocks the domain for being registered for a random period of time.
So the procedure should be as follows
The text was updated successfully, but these errors were encountered: