Call To Action

In a bid to create more awareness around COVID-19 Government has called on all .za domain name holders that have an associated website to create a landing page with a visible link to www.sacoronavirus.co.za. For more details see section 5.1.4 of Regulation No. 43164 published on 26 March 2020.

ZA Contact Update


Table of Contents

1.
Performing the Contact Update Request
2. Possible Responses
  2.1. 1000: Contact Update Successful
  2.2. 2303: Contact Does Not Exist
  2.3. 2004: Internationalized Address Requires Only ASCII
  2.4. 2306: Address Information Cannot Be Empty
  2.5. 2201: Incorrect Owner
3. Example E-Mail
4. Removing Postal Info Types of "loc" and "int"


EPP Contact Update


Notes

1. The <contact:id> element is the unique identification code for the contact that must be updated.

2. The <contact:update> element specifies to the server that an update command must be performed.

3. The <contact:chg> element specifies to the server that a change has to be applied to the contact.

4. The <contact:add> element specifies the statuses that must be applied to the contact.

5. The <contact:rem> element specifies the statuses that must be removed from the contact. Certain statuses may clash and have to be removed in specific order.

6. All associated information may be updated except for the <contact:id> element.

7. All ZA Namespaces do not make use of the <contact:disclose> element.

8. All updates to contact objects must include the <contact:cc> element.

9. All updated will send a notification email to the contact email address.

10. The update will only be executed at the end of a 5 day period.

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <command>
    <update>
      <contact:update
       xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
        <contact:id>ContactID</contact:id>
        <contact:add>
          <contact:status s="clientUpdateProhibited"/>
        </contact:add>
        <contact:rem>
          <contact:status s="clientUpdateProhibited"/>
        </contact:rem>
        <contact:chg>
          <contact:postalInfo type="int">
            <contact:name>New Name</contact:name>
            <contact:org>New Organisation</contact:org>
            <contact:addr>
              <contact:street>New Street 1</contact:street>
              <contact:street>New Street 2</contact:street>
              <contact:city>New City</contact:city>
              <contact:sp>New Province</contact:sp>
              <contact:pc>2222</contact:pc>
              <contact:cc>CC</contact:cc>
            </contact:addr>
          </contact:postalInfo>
          <contact:postalInfo type="loc">
            <contact:name>New Name</contact:name>
            <contact:org>New Organisation</contact:org>
            <contact:addr>
              <contact:street>New Street 1</contact:street>
              <contact:street>2New Street 2</contact:street>
              <contact:city>New City</contact:city>
              <contact:sp>New Province</contact:sp>
              <contact:pc>2222</contact:pc>
              <contact:cc>CC</contact:cc>
            </contact:addr>
          </contact:postalInfo>
          <contact:voice>+27.115551234</contact:voice>
          <contact:fax/>
          <contact:email>new@email.gtld</contact:email>
          </contact:disclose>
        </contact:chg>
      </contact:update>
    </update>
  </command>
</epp>

 

 

Possible Responses


The following are possible responses from our server.

1001: Contact Update Pending

A response code of 1001 means that the update was successful and all changes will be applied at the end of te 5 day period.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="1001">
      <epp:msg>Contact Update Pending</epp:msg>
    </epp:result>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-13EE4F639C6-4C81</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

2303: ID Does Not Exist

A response code of 2303 means that the contact you attempted to update does not exist in the database of the registry. Please ensure that the specified <contact:id> value is correct.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="2303">
      <epp:msg>ID does not exist</epp:msg>
    </epp:result>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-13EE4EFC051-B5CCB</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

2004: Internationalised contact address must only contain ascii characters.

A response code of 2004 means that the <postalInfo type="int"> element was updated and the changed information contained UTF8 characters. Please review the provided information within the element to ensure only ASCII values are present.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="2004">
      <epp:msg>Internationalised contact address must only contain ascii characters.</epp:msg>
    </epp:result>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-13EE4FC9E02-5FE12</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

 

2306: Contact address information Name and City elements cannot be empty

A response code of 2306 means that either the <contact:city> or <contact:name> elements were attempted to be updated with null values. Performing this type of update is against current policy. Please populate the required fields or omit the elements from the update.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="2306">
      <epp:msg>Contact address information Name and City elements cannot be empty</epp:msg>
    </epp:result>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-13EE52338FA-1DEC4</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

 

2201: Requester != Contact Owner ID

A response code of 2201 means that the contact ID provided for the update is not registered by you, but rather belongs to another registrar. Please review the specified value in the <contact:id> element.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="2201">
      <epp:msg>Requester != Contact Owner ID</epp:msg>
    </epp:result>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-13EE5775C37-7C11D</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

 


Example E-Mail Sent to Registrant

The e-mail example below is an example of what a contact will receive when an update is performed on their information.

Dear Registrant,


Please be advised that the contact details for "John New Rant" have been updated as detailed below.

Should you have any queries in this regard, please contact your Registrar myRegistrar at
+27.115550912 or myRar@rar.co.za

Current Contact Information:
  ID:    JNR001 
  Phone:  +27.115551234
  Fax:    +86.5551234
  Email:  JNR@rantEmail.co.za

Current Contact Localized Postal Address:
  Name:    John Old Rant
  Street:  12 Old Place
  Street:  Old Street
  Street:  Old Town
  Org:    None
  City:    Registrant Ville
  Province: Gauteng
  Country: ZA
  Code:    90210


New Contact Information:
  ID:    JNR001 
  Phone:  +27.110003333
  Fax:    +27.119990000
  Email:  JNR@newRantEmail.co.za

New Contact Localized Postal Address:
  Name:    John New Rant
  Street:  21 New Place
  Street:  New Street
  Street:  New Town
  Org:    None
  City:    New Registrant Ville
  Province:Gauteng
  Country: ZA
  Code:    01209


Additional Information:
  Status:
    ok

Removing "loc" or "int" Postal Information


If a contact object contains both "loc" and "int" postal information type, either can be removed to no longer be shown as part of the contact postal information.
For the example below, the contact contains both types, and the "int" postal type will be removed.

Contact info shows both types

 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
  <epp:response>
    <epp:result code="1000">
      <epp:msg>Contact Info Command completed successfully</epp:msg>
    </epp:result>
    <epp:resData>
      <contact:infData>
        <contact:id>testRant</contact:id>
        <contact:roid>CTC_2F-COZA</contact:roid>
        <contact:status s="ok"/>
        <contact:postalInfo type="int">
          <contact:name>Int Name</contact:name>
          <contact:org>Example Organisation</contact:org>
          <contact:addr>
            <contact:street>Int Street</contact:street>
            <contact:street>Int Place</contact:street>
<contact:street>Int Area</contact:street>
            <contact:city>Int City</contact:city>
            <contact:sp>Int Province</contact:sp>
            <contact:pc>9999</contact:pc>
            <contact:cc>ZA</contact:cc>
          </contact:addr>
        </contact:postalInfo>
        <contact:postalInfo type="loc">
          <contact:name>Local Name</contact:name>
          <contact:org/>
          <contact:addr>
            <contact:street>1 Fake Street</contact:street>
            <contact:street>12 Fake Place</contact:street>
            <contact:street>Fake Area</contact:street/>
            <contact:city>Registrant Ville</contact:city>
            <contact:sp>Rant Province</contact:sp>
            <contact:pc>9998</contact:pc>
            <contact:cc>ZA</contact:cc>
          </contact:addr>
        </contact:postalInfo>
        <contact:voice>+27.113456789</contact:voice>
        <contact:fax>+27.119876543</contact:fax>
        <contact:email>example@example.com</contact:email>
        <contact:clID>myRar</contact:clID>
        <contact:crID>myRar</contact:crID>
        <contact:crDate>2012-06-11T09:24:15Z</contact:crDate>
        <contact:upID>myRar</contact:upID>
        <contact:upDate>2012-06-11T09:24:15Z</contact:upDate>
      </contact:infData>
    </epp:resData>
    <epp:trID>
      <epp:svTRID>DNS-EPP-137DBD6D649-56A04</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

To remove either type, perform a Contact Update Command to remove ALL current existing elements. For the example, the "int" type will be removed as follows.

NOTE:
The <contact:name> and <contact:city> elements must be a single white-space. If they are not, the update will not be successful.

 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <command>
    <update>
      <contact:update
       xmlns:contact="urn:ietf:params:xml:ns:contact-1.0">
        <contact:id>testRant</contact:id>
        <contact:chg>
          <contact:postalInfo type="int">
            <contact:name> </contact:name>
            <contact:org></contact:org>
            <contact:addr>
              <contact:street></contact:street>
              <contact:street></contact:street>
              <contact:street></contact:street>
              <contact:city> </contact:city>
              <contact:sp></contact:sp>
              <contact:pc></contact:pc>
              <contact:cc>ZA</contact:cc>
            </contact:addr>
          </contact:postalInfo>
        </contact:chg>
      </contact:update>
    </update>
  </command>
</epp>

From the above, the "int" type will be removed from the contact object and the "loc" type will always show when retrieving contact information.

 

Last update: 20-05-2014 10:38:01

festive season

As the end of the year approaches, please keep in mind the following information to avoid any frustrations over the holiday period.

 

Closure Date:

Our offices will be closed from the 21st of December 2020 and will reopen on the 4th of January 2021. We will have skeleton staff on standby to attend to urgent customer queries.

 

Contact details:
EPP and Legacy Support: support@registry.net.za
EPP and Legacy Accounts: accounts@registry.net.za 
Legal: legal@registry.net.za

 

Happy holidays and let us continue to maintain social distancing as we approach this peak time!

 

ZACR Team

 

Technical Support

All issues and questions relating to the co.za EPP Registry Registrar System must be raised in the Contact/Support pages through the Registrar Portal. This is to ensure that our support department tracks and addresses all issues. Log in to the Registrar Portal and submit a support request online.

 

Registrar Noticeboard

Click here for the latest status updates.

日日摸夜夜添夜夜添无码_最新亚洲中文字幕一区在线_尹人香蕉视频在线观看