Search in this section
On this page you will find the AutoDNS DIRECT changelog for 2017.
General, XML Interface (API), TLD Policies, User Interface
New ICANN Ownerchange Procedure for gTLDs and new gTLDs from 12-07-2016
ICANN (Internet Corporation for Assigned Names and Numbers) has introduced a new mandatory owner change procedure which will be put into action on December 7, 2016.
As always, we have focused on keeping modifications on existing processes to a minimum for you.
The following request types and updates are affected:
- Updates of domains with a new owner contact (Domain Update)
- Updates of existing contacts if the name, the organization or the email address change (Domain Contact Update)
- Incoming domain transfers, if the name, the organization or the email address change (Domain Transfer)
In the future, when issuing a relevant request, you must explicitly confirm that the changes being made are on behalf of the domain registrant. This mandatory change of confirmation affects both the user interface and XML API.
To confirm modifications for a domain update, transfer (single or bulk) or a contact update in the user interface, you need to select the new checkbox (“I hereby confirm the changes on behalf of the domain owner"). This only applies for gTLDs and new gTLDs.
Please be aware that this change will affect your current implementation of the XML API. Set the corresponding key (<confirm_owner_consent>1<confirm_owner_consent>) for the XML API to confirm that the request is being made on behalf of the domain registrant.
The respective XML templates can be found here:
As soon as the changes have been made to the registrant data, the old and new registrant will automatically be informed via email. An additional confirmation of the registrant is not needed. The sender name of the email that is sent to the registrant can be configured similarly to the IRTP-process in your user profile.
After an owner change of a gTLD domain, the domain is automatically locked against outgoing transfers if it was not locked beforehand. This transfer lock can be removed by starting a domain status update request.