Date: Fri, 29 Mar 2024 15:18:23 +0100 (CET) Message-ID: <506339679.3969.1711721903659@de.help.internetx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3968_1962331093.1711721903656" ------=_Part_3968_1962331093.1711721903656 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The AutoDelete function automatically deletes expired domains. AutoDelet= e is only available on request to our sales department and can only be acti= vated for an entire customer but not for individual users.
Generalized domain lifecycle
The InterNetX AutoDelete funct=
ion deletes expired domains automatically. AutoDelete only works for certai=
n TLDs. Only the AutoDelete TLDs are automatically deleted on their expirat=
ion date. TLDs which are not on the AutoDelete TLD list are configured to r=
enew the domains automatically on their respective expiration date. =
An overview of AutoDelete TLDs can be seen via a filter in our TLD knowledge base. There are two methods of sending a request to the system (U=
ser Interface and XML API) in order to inquire and then renew domains. Acci=
dentally deleted domains can be restored either before or after your accoun=
t is migrated to the AutoDelete mode.
For .DE domains, AutoDelete returns the domain (TR= ANSIT) to the respective registry instead of deleting it. This means that t= hese domains cannot be restored. The holder receives mail from the registry= . Alternatively, it is possible to delete .DE domains manually at the end o= f the registration period (Expire). More information about the .DE transit = can be found at Denic.
For further details about the XML interface and XML requests please see = the AutoDNS XML Interface Documentation, which you can download here.
Existing AutoRenew accounts ca= n be migrated to AutoDelete.
Please be aware that once your account has been mi= grated to AutoDelete mode, the changes cannot be undone.
|
The steps in detail |
---|---|
|
You apply for an AutoDelete account. |
= |
We transform your AutoRenew account into an A= utoDelete demo mode account. |
|
Preliminary cleaning procedure: First, = you have to decide which of your domains that will be expiring during the n= ext 33 days, you want to renew or delete. Second, renew or dele= te your domains in the AutoDNS user interface or via the XML interface. If = you want to undo domain deletion, you can use the restore function either b= efore or after the migration to AutoDelete mode. For details about re= newing, deleting and restoring domains see the following chapters of the Qu= ickGuide. Click a link to switch to the desired chapter. |
|
|
The switch from the demo to the live mode is only possible after all con= cerned domains have been renewed or deleted. |
|
|
After you have finished the preliminary domai= n cleaning procedure, contact us immediately. |
|
We enable your AutoDelete account as soon as = possible. |
This process is complaint with ICANN's "Expired Registration Recovery Po= licy (2.1. Expiration Reminder Notices)": https://www.ica= nn.org/resources/pages/errp-2013-02-28-en
Several emails will be automatically sent to the domain owner during the=
AutoDelete process. You can specify the details about the sender in the General AutoDelete Email Settings section.
Name of the Sender |
Add a sender name here to let your customers = know that the email originates from you. The term"/ Domain Robo= t" is added automatically. It cannot be changed. |
Reply-to Address |
Enter your custom reply-to email address here= . |
BCC Address |
You can enter an additional BCC email address= here. |
Click the Expiring Domains entry in the menu group
The following domains are listed in this overview:
The following details are displayed: <= /p>
Possible values:
You also can renew expiring domains in the toolbar of this overv= iew:
You also can restore expiring domains in the toolbar of this ove= rview:
Click the button Restore Deleted Domains to switch to t= he Domain Restore Overview allowing you to restore the exp= iring domains.
With this task you can inquire all expiring domains.
XML example for the system re= quest
<requ= est> <auth> <user>customer</user> <password>test</password> <context>4</context> </auth> <task> <code>0718</code> </task> </request> XML Example for the System Response
XML example for the system re= sponse
<resp= onse> <result> <data>=20 <domain>=20 <changed>2012-07-06 12:10:02</changed>=20 <created>2012-06-06 00:00:03</created>=20 <domain>example.com</domain>=20 <payable>2012-07-13 00:00:00</payable> <payment_limit>2012-07-12 00:00:00</payment_limit&= gt;=20 <status>notify_5</status>=20 </domain>=20 <domain>=20 <changed>2012-07-07 12:10:01</changed>=20 <created>2012-06-07 00:00:02</created>=20 <domain>example.net</domain>=20 <payable>2012-07-14 00:00:00</payable>=20 <payment_limit>2012-07-13 00:00:00</payment_limit&= gt;=20 <status>notify_5</status>=20 </domain>=20 <domain>=20 <changed>2012-07-07 21:10:00</changed>=20 <created>2012-06-07 09:00:02</created>=20 <domain>example.org</domain>=20 <payable>2012-07-14 08:43:16</payable>=20 <payment_limit>2012-07-13 08:43:16</payment_limit&= gt;=20 <status>notify_5</status>=20 </domain>=20 <summary>3</summary>=20 </data>=20 <status>=20 <code>S0718</code>=20 <text>Autodelete entries were inquired successfully.</= text>=20 <type>success</type>=20 </status>=20 </result> </response>
These information is part of the system response
Key | = Description |
---|---|
domain |
Domain information bloc |
domain / changed |
Date of the last update |
domain / created |
Date of AutoDetete process start |
domain / domain |
Domain name |
domain / payable |
Payable date of the domain |
domain / payment_limit |
Point in time when the domain has to be paid = for a renew. |
domain / status |
Current domain status Values:
|
The Inventory List menu item contains two options.
Domain Data
In this section, you can define the settings for the domain renew here.&= nbsp;
If you have selected domains before switching to the Renew function, they will be displayed together in the Domain Name = strong>entry field.
Entry details:
Domain Name(s), Payable |
Enter the domain name date here. For a = bulk request press Enter or click the Bulk M= ode link, if available. |
Renew Period |
Select the desired renew period. Please note that registries have their own terms concerning the length o= f possible minimum and maximum registration period that applies to their TL= D. |
Key |
Occurs |
Format |
Description |
---|---|---|---|
code |
1 |
task |
DomainRenew code: 0101003 |
domain |
1 - n |
||
domain / name |
1 |
string |
Domain name |
domain / payable |
1 |
date time |
Billing date The billing date can be displayed with the task DomainInquire. |
domain / period |
0 - 1* |
int |
The number of years the registration period w= ill be renewed for. |
domain / remove_cancellation |
0 - 1 |
enum |
With this tag you can renew the domains and d= elete existing cancelations at once. Should an existing re= quest for cancelation be deleted? yes =3D the cancelation request wil= l be deleted. no =3D the cancelation request will not be deleted. =Default: no When =E2=80=9Cno=E2=80=9D: If there is a current cance= lation request the request will fail. |
XML example for the system request
<requ= est> <auth>=20 <user>customer</user>=20 <password>test</password>=20 <context>1</context>=20 </auth>=20 <task>=20 <code>0101003</code>=20 <domain>=20 <name>example.com</name>=20 <payable>2009-09-16</payable> <period>1</period>=20 <remove_cancellation>yes</remove_cancellation> </domain> </task> </request>
XML example for the system respons= e
<resu= lt>=20 <status>=20 <code>N0101003</code> <object>=20 <type>domain</type>=20 <value>example.com</value>=20 </object> <text>Domain renew has been started successfully.</text= >=20 <type>notify</type>=20 </status>=20 </result>
For further details about the XML interface and XM= L requests please see the AutoDNS XML Interface Documentation, which you ca= n download here.
You can delete the desired domains in the AutoDNS user interface or via = the XML interface.
To prevent automatic transit for .DE AutoDelete domains, you can delete = the domains manually at expiry.
With this task you can create a cancelation in the system of a domain by= specifying the cancelation data.
As long as the cancelation is not executed, it is possible to inquire, u= pdate or delete the request.
Key | Occurs |
Format |
Description |
---|---|---|---|
code |
1 |
task |
CancelationCreate code: 0103101 |
cancelation |
1 - n |
||
cancelation / domain |
1 |
string |
The domain name |
cancelation / type |
1 |
enum |
Cancelation types. Values:
|
cancelation / execdate |
0 - 1 |
string |
Execution date. Values:
|
XML example for the system request
<requ= est> <auth>=20 <user>customer</user>=20 <password>password</password>=20 <context>4</context>=20 </auth>=20 <task>=20 <code>0103101</code>=20 <cancelation>=20 <domain>example.com</domain> <type>delete</type>=20 <execdate>expire</execdate>=20 </cancelation>=20 <reply_to>customer@example.com</reply_to>=20 </task>=20 </request>
XML example for the system response
<?xml= version=3D"1.0"encoding=3D"utf-8" ?> =20 <response>=20 <result> <data>=20 <cancelation> <created>2009-05-1311:02:42</created> = =20 <domain>example.com</domain>=20 <execdate>2012-12-0312:14:27</execdate>=20 <type>DELETE</type>=20 </cancelation>=20 </data>=20 <status>=20 <code>S0103101</code> <text>Cancelation has been transmitted successfully.</te= xt>=20 <type>success</type>=20 </status> </result> </response>
A domain that is not renewed before or at the end of the registration pe= riod will be automatically deleted by the system. To restore a domain= that has been deleted, please use the AutoDNS Domain Restore function avai= lable in either the user interface or API. Please note that deleted domains= can only be restored within a certain timeframe.
For .DE domains, AutoDelete returns the domain (TRANSIT) to the respecti= ve registry instead of deleting it. This means that these domains cannot be= restored. The holder receives mail from the registry. Alternatively, it is= possible to delete .DE domains manually at the end of the registration per= iod (Expire). More information about the .DE transit can be found at Denic= .
You can easily switch from the Expiring Domains overvie= w to the Domain Restore overview.
Click the button Restore Deleted Domains in the too=
lbar and you will be redirected to the Domain Restore over=
view.
In the Domain Restore Overview you can see all deleted domains, that can be=
restored.
With this task you can display all restorable domains in your account.&n= bsp;
Please be aware that only domains marked with the action RESTORE_ARGP (= =3D Auto Renew Grace Period) will be restored free of charge.
A domain restore for domains marked with the action RESTORE_RGP (=3D Red= emption Grace Period is always associated with costs. Please see the curren= t price list.
XML example for t= he system request
<requ= est> =20 <auth>=20 <user>customer</user>=20 <password>password</password>=20 <context>4</context>=20 </auth>=20 <task>=20 <code>0105005</code> <where>=20 <key>name</key>=20 <operator>like</operator>=20 <value>*</value>=20 </where>=20 <view>=20 <offset>0</offset> <limit>3</limit>=20 <children>0</children> </view>=20 <key>owner</key>=20 <key>created</key>=20 <key>payable</key> <key>ownerc</key>=20 <key>adminc</key> <key>techc</key>=20 <key>zonec</key>=20 <key>nserver</key>=20 <key>authinfo</key>=20 <key>registry_status</key> <key>expire</key>=20 <ctid>ABCDEFG</ctid>=20 </task> </request>
XML example for the system response
<resp= onse> =20 <result> =20 <data>=20 <summary>2</summary>=20 <restore>=20 <name>example.com</name>=20 <expire>2011-12-23 15:35:54</expire>=20 <payable>2012-02-15 15:44:41</payable>=20 <ownerc>458922</ownerc>=20 <adminc>458922</adminc> =20 <techc>458922</techc> <zonec>458922</zonec>=20 <registry_status>LOCK</registry_status>=20 <nserver>=20 <name>ns1.example.com</name>=20 </nserver>=20 <nserver>=20 <name>ns2.example.com</name>=20 </nserver>=20 <action>RESTORE_ARGP</action> <authinfo>Y8HKJXgCupOZAWx</authinfo>=20 <owner>=20 <user>customer</user>=20 <context>4</context>=20 </owner>=20 <created>2012-08-15 15:44:41</created>=20 </restore>=20 <restore>=20 <name>example.com</name>=20 <expire>2011-12-23 15:35:54</expire>=20 <payable>2012-02-15 15:44:41</payable>=20 <ownerc>458922</ownerc>=20 <adminc>458922</adminc> =20 <techc>458922</techc>=20 <zonec>458922</zonec>=20 <registry_status>LOCK</registry_status>=20 <nserver>=20 <name>ns1.example.com</name>=20 </nserver>=20 <nserver>=20 <name>ns2.example.com</name> </nserver>=20 <action>RESTORE_ARGP</action>=20 <authinfo>Y8HKJXgCupOZAWx</authinfo>=20 <owner>=20 <user>customer</user>=20 <context>4</context>=20 </owner>=20 <created>2011-02-15 15:44:41</created>=20 </restore>=20 </data>=20 <status>=20 <code>S0105005</code>=20 <type>success</type>=20 </status> =20 </result> =20 </response>
Form section details:
Domains |
The domains you have selected in the = Domain Restore overview are listed here. You can add additional do= mains. Press Enter to separate the entries. |
Target User |
You can assign a restored domain to another user here. Click , to selec= t the owner in a list. Click , to enter the logged in user as owner. |
I confirm that I accept all charges associate= d with restoring domains that are within the RGP restore phase. To view whi= ch domains are in the RGP restore phase, go back to the Domain Restore over= view by clicking on the Cancel button below. |
Activate the checkbox to restore domains in t= he RGP phase. Otherwise a restore is not possible. |
With this task you can restore deleted domains. You also can restore and= renew domains in one request.
XML example for the system request
<requ= est> <auth>=20 <user>customer</user>=20 <password>password</password>=20 <context>4</context>=20 </auth>=20 <task>=20 <code>0101005</code>=20 <domain>=20 <name>example.com </name>=20 </domain>=20 <reply_to>customer@example.com</reply_to>=20 <ctid>ABCDEFGH</ctid>=20 </task>=20 </request>
XML example for the system response
<resp= onse> =20 <result>=20 <data/>=20 <status>=20 <code>N0101005</code>=20 <type>notify</type> <object>=20 <type>domain</type>=20 <value>example.com</value>=20 </object>=20 </status>=20 </result> </response>
XML example for the system request
<requ= est> <auth>=20 <user>customer</user>=20 <password>password</password>=20 <context>4</context>=20 </auth>=20 <task>=20 <code>0101005</code>=20 <domain>=20 <name>example.com</name>=20 <action>RESTORE_RENEW</action>=20 </domain>=20 <reply_to>customer@example.com</reply_to> <ctid>ABCDEFG</ctid>=20 </task> </request>
XML example for the system response
<resp= onse> =20 <result> =20 <data/>=20 <status> <code>N0101005</code>=20 <type>notify</type> <object>=20 <type>domain</type>=20 <value>example.com</value>=20 </object>=20 </status>=20 </result> </response>