Date: Thu, 28 Mar 2024 15:08:38 +0100 (CET) Message-ID: <1633078562.3695.1711634918153@de.help.internetx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3694_79881579.1711634918149" ------=_Part_3694_79881579.1711634918149 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The contact update command updates an existing contact. If the contact i= s used at different registries, the respective updates are carried out asyn= chronously and a system messag= e is provided when polling.
<epp x= mlns=3D"urn:ietf:params:xml:ns:epp-1.0"> <command> <update> <contact:update xmlns:contact=3D"urn:ietf:params:xml:ns:cont= act-1.0"> <contact:id>11268444</contact:id> <contact:chg> <contact:postalInfo type=3D"loc"> <contact:addr> <contact:street>124 Example Dr.</conta= ct:street> <contact:street>Suite 200</contact:str= eet> <contact:city>Dulles</contact:city> <contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>US</contact:cc> </contact:addr> </contact:postalInfo> <contact:email>jon.doe@domain.com</contact:ema= il> <contact:voice>+1.7034444444</contact:voice>= ; </contact:chg> </contact:update> </update> <clTRID>ABC-12345</clTRID> </command> </epp>
<epp x= mlns:domain=3D"urn:ietf:params:xml:ns:domain-1.0" xmlns:domainrobot=3D"urn:= org:domainrobot:ns:ext-1.0" xmlns:contact=3D"urn:ietf:params:xml:ns:contact= -1.0" xmlns:pro=3D"urn:org:domainrobot:ns:contact:pro-1.0" xmlns:ro=3D"urn:= org:domainrobot:ns:contact:ro-1.0" xmlns:xxx=3D"urn:org:domainrobot:ns:cont= act:xxx-1.0" xmlns:ca=3D"urn:org:domainrobot:ns:contact:ca-1.0" xmlns:cat= =3D"urn:org:domainrobot:ns:contact:cat-1.0" xmlns=3D"urn:ietf:params:xml:ns= :epp-1.0" xmlns:jobs=3D"urn:org:domainrobot:ns:contact:jobs-1.0" xmlns:rgp= =3D"urn:ietf:params:xml:ns:rgp-1.0" xmlns:aero=3D"urn:org:domainrobot:ns:co= ntact:aero-1.0" xmlns:host=3D"urn:ietf:params:xml:ns:host-1.0" xmlns:hk=3D"= urn:org:domainrobot:ns:contact:hk-1.0" xmlns:bank=3D"urn:org:domainrobot:ns= :contact:bank-1.0" xmlns:it=3D"urn:org:domainrobot:ns:contact:it-1.0" xmlns= :barcelona=3D"urn:org:domainrobot:ns:contact:barcelona-1.0" xmlns:au=3D"urn= :org:domainrobot:ns:contact:au-1.0" xmlns:uk=3D"urn:org:domainrobot:ns:cont= act:uk-1.0" xmlns:swiss=3D"urn:org:domainrobot:ns:contact:swiss-1.0" xmlns:= ru=3D"urn:org:domainrobot:ns:contact:ru-1.0"> =09<response> =09=09<result code=3D"1000"> =09=09=09<msg lang=3D"en">Command completed successfully</msg> =09=09</result> =09=09<trID> =09=09=09<clTRID>ABC-12345</clTRID> =09=09=09<svTRID>DEF-12345</svTRID> =09=09</trID> =09</response> </epp>
Note
The existing TLD / contact extensions are always transmitted and merged = when they are updated. Below are several examples which cover certain opera= tions.
The extension website of the TLD .jo= bs is to be updated. The original value was "myhomepage.com" and is to be updated = to "mynewhomep= age.com". It is important to always send the complete block when updati= ng.
<jobs:= contact xmlns:jobs=3D"urn:org:domainrobot:ns:contact:jobs-1.0"> =09<jobs:adminType>0</jobs:adminType> =09<jobs:contactTitle>Herr</jobs:contactTitle> =09<jobs:hrMember>0</jobs:hrMember> =09<jobs:website>mynewhomepage.com</jobs:website> </jobs:contact>
The extension website of the TLD .jobs is to b= e deleted. In order to achieve this, the respective extensions is left empt= y. It is important to always send the complete block when updating.
<jobs:= contact xmlns:jobs=3D"urn:org:domainrobot:ns:contact:jobs-1.0"> =09<jobs:adminType>0</jobs:adminType> =09<jobs:contactTitle>JOBS_CONTACT_TITLE</jobs:contactTitle> =09<jobs:hrMember>0</jobs:hrMember> =09<jobs:website/> </jobs:contact>
All extensions are to be removed for the extensions of the TLD .jobs. Th= e respective block must be left empty.
<jobs:= contact xmlns:jobs=3D"urn:org:domainrobot:ns:contact:jobs-1.0"/>