Date: Thu, 28 Mar 2024 20:37:55 +0100 (CET) Message-ID: <1820298419.3747.1711654675036@de.help.internetx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3746_1154260922.1711654675032" ------=_Part_3746_1154260922.1711654675032 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Complete automation of the extension of the duration of a domain. This a= ction requires two steps, retrieving the domain data to determine the expir= ation date and extending the domain duration with the expiration date.
The required expiration date is queried via the DomainInfo comm= and. It is contained in the exDate tag in the system response.
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <command> <info> <domain:info xmlns:domain=3D"urn:ietf:params:xml:ns:domain-1= .0"> <domain:name hosts=3D"all">domain.com</domain:name= > </domain:info> </info> <clTRID>ABC-12345</clTRID> </command> </epp>
<epp xmlns:domain=3D"urn:ietf:params:xml:ns:domain-1.0"> <response> <result code=3D"1000"> <msg lang=3D"en">Command completed successfully</msg&g= t; </result> <resData> <domain:infData> <domain:name>domain.com</domain:name> <domain:roid>11109997-domain.com</domain:roid> <domain:registrant>23022508</domain:registrant> <domain:contact type=3D"admin">23022508</domain:co= ntact> <domain:contact type=3D"tech">23022508</domain:con= tact> <domain:ns> <domain:hostAttr> <domain:hostName>ns1.nameserver.com</domai= n:hostName> </domain:hostAttr> <domain:hostAttr> <domain:hostName>ns2.nameserver.com</domai= n:hostName> </domain:hostAttr> </domain:ns> <domain:clID>user1, 4</domain:clID> <domain:crID>user1, 4</domain:crID> <domain:crDate>2017-07-31T14:44:41.000Z</domain:cr= Date> <domain:upID>user1, 4</domain:upID> <domain:upDate>2017-07-31T09:06:49.000Z</domain:up= Date> <domain:exDate>2018-07-31T14:44:41.000Z</domain:ex= Date> <domain:authInfo> <domain:pw>123ABC456DEF</domain:pw> </domain:authInfo> </domain:infData> </resData> <extension> <domainrobot:domain xmlns:domainrobot=3D"urn:org:domainrobot= :ns:ext-1.0"> <domainrobot:zonec>23022508</domainrobot:zonec> <domainrobot:trustee>0</domainrobot:trustee> <domainrobot:privacy>0</domainrobot:privacy> </domainrobot:domain> </extension> <trID> <clTRID>ABC-12345</clTRID> </trID> </response> </epp>
The registration period of a domain can be extended with the DomainR=
enew command. The length of the renew is set with the period tag. In t=
he tag curExpDate
the value from exDate
is set.=
p>
The possible registration periods that can be used for a DomainRenew= depend on the TLD.
By setting a clTRID
, the poll message for this request can =
be assigned. In this example <clTRID>EXAMPLE-123456789</clTR=
ID>
is used.
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <command> <renew> <domain:renew xmlns:domain=3D"urn:ietf:params:xml:ns:domain-= 1.0"> <domain:name>domain.com</domain:name> <domain:curExpDate>2020-05-22</domain:curExpDate&g= t; <domain:period unit=3D"y">0</domain:period> </domain:renew> </renew> <clTRID>EXAMPLE-123456789</clTRID> </command> </epp>
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0" xmlns:domain=3D"urn= :ietf:params:xml:ns:domain-1.0"> <response> <result code=3D"1001"> <msg lang=3D"en">Command completed successfully; action p= ending</msg> </result> <resData> <domain:renData> <domain:name>domain.com</domain:name> </domain:renData> </resData> <extension /> <trID> <clTRID>EXAMPLE-123456789</clTRID> </trID> </response> </epp>
The DomainRenew command automatically generates a job that take= s care of the renewal process. As soon as the job is finished, a poll messa= ge is generated that can be inquired with the PollInfo command.
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"> =09<command> =09=09<poll op=3D"req" /> =09=09<clTRID>ABC-12345</clTRID> =09</command> </epp>
<epp x= mlns=3D"urn:ietf:params:xml:ns:epp-1.0"> =09<response> =09=09<result code=3D"1301"> =09=09=09<msg lang=3D"en">Command completed successfully; ack to dequ= eue</msg> =09=09</result> =09=09<msgQ count=3D"2" id=3D"880178"> =09=09=09<qDate>2017-07-14T06:52:19.000Z</qDate> =09=09=09<msg>Message text</msg> =09=09</msgQ> =09=09<resData> =09=09=09<!-- See polling section for different message results --> =09=09</resData> =09=09<trID> =09=09=09<clTRID>1cb47efe-2ab3-4769-b0cb-3252af528095</clTRID> =09=09=09<svTRID>20170714-app2-dev-10055</svTRID> =09=09</trID> =09</response> </epp>
In order to assign a poll message to a domain registration, a clTR=
ID
(ClientTransactionId) can be used for which the following is impo=
rtant:
<clTRID>EXAMPLE-123456789</clTRID>
The returned clTRID
is the same as the one that was used for t=
he previous DomainCreate command. The polling system works under t=
he first-in-first-out (FIFO) principle. The poll message is therefore retur=
ned until it is confirmed. To confirm a poll message with the PollConfi=
rm request, the ID from the previous command is requi=
red.
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"> =09<command> =09=09<poll op=3D"ack" msgID=3D"627787" /> =09=09<clTRID>ABC-12346</clTRID> =09</command> </epp>
<epp xmlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <response> <result code=3D"1000"> <msg lang=3D"en">Command completed successfully</msg&g= t; </result> <msgQ count=3D"0" id=3D"627787" /> <trID> <clTRID>ABC-12346</clTRID> </trID> </response> </epp>