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 Polling and Acking Messages

Background Information: A poll message will be sent to a registrar for every action that is pending. This includes:

 

  • - Contact Updating
  • - Domain Updating
  • - Domain Deleting
  • - Domain Transfering

Any of the above mentioned actions have a period of time in which they are pending. This will result in a poll message being added to a message queue. This section will look at the following:

 

  • - Requesting queued messages
  • - Acking queued messages
  • - Possible contact messages
  • - Possible domain messages


NOTE:
 

1. Accreditation for this section is only considered complete when the queue has been emptied (result code 1300, no messages remaining).
2. The ZACR will never perform reverse polling. This means that teh ZACR will never poll the server or system of any registrar.

Requesting a Queued Message

 

Poll messages awaiting in the queue can be retrieved using the EPP Poll command. To send the poll command, the <poll op="req"/> element has to be included. The attribute op refers to the operation that the poll command must perform. A value of req for the op attribute means that the operation to be performed by the poll command is a request for queued messages.

 

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <command>
    <poll op="req"/>
  </command>
</epp>

 


<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="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T11:21:00.086+02:00</epp:qDate>
      <epp:msg>MESSAGE</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <contact:panData>
        <contact:id paResult="1">ContactID</contact:id>
        <contact:paTRID>
          <epp:clTRID>CLTRID-13028592426-DUKR</epp:clTRID>
          <epp:svTRID>ZACR-EPP-12F58765CB2-116CA</epp:svTRID>
        </contact:paTRID>
        <contact:paDate>2011-04-15T09:20:59Z</contact:paDate>
      </contact:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028592638-BZ9V</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F5876A0B4-14CF7</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>


Interpretation of received poll message:

 

  •  - A result code of 1301 means that there was at least 1 message in the message queue. The result will also contain the message. See below for an example of a 1301 response.
  •  - If the poll command was sent correctly, the server will respond with either a result code of 1300 or 1301.
  •  - A result code of 1300 means that there are no messages in the message queue.
  • - The <epp:mgsQ> element contains information about the command that yielded the poll message. the count attribute shows the message count queued. The id attribute will contain a value that shows the unique tracking id of the message. This id will be used to ack the message.
  • - The <epp:resData> element contains information about what the command result was.
  • - The <epp:trID> element contains the unique tracking ID of the poll command.

 

Polling for messages allows messages to move up in the message queue, meaning that other messages awaiting in the queue can only be retrieved once the messages in front of them are requested and acknowledged.

 

Acknowledging Poll Messages

 

If a message as been polled for and there is no longer a need for the message, it must be acknowledged. Acknowledging a message will result in the message being removed from the queue, allowing other messages to be retrieved.

Note:
Messages are queued in a "First-In-First-Out" order. It is therefore advised that messages are polled for on a constant basis so as to avoid a very large message queue.

To acknowledge a message, a poll command must be sent. In the command the following elements are required:

 

  • - <poll op="ack" msgID="12345"> : The op attribute with a value of ack indicates to the server that a poll command must be performed where the operation is to ack a message. The message to be acked must be specified. To specify the message, include the message id; obtained through the above example; in the msgID attribute.
  • - <clTRID> : A unique ID of a minimum of 8 characters must be used. The ID can later be used to acquire a poll message about the acking of a message.

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
    <command>
      <poll op="ack" msgID="ABC-123"/>
      <clTRID>ABC-12346</clTRID>
    </command>
</epp>

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
  <response>
    <result code="1000">
      <msg>Command completed successfully</msg>
    </result>
    <msgQ count="1" id="ABC-123"/>
    <trID>
      <clTRID>ABC-12346</clTRID>
      <svTRID>54322-XYZ</svTRID>
    </trID>
  </response>
</epp>

 

Contact Poll Messages

 

This section looks at the possible message responses that can be received when polling for a message where the information contained refers to registrants.

 

Contact Update Pending

 

A message similar to the one below will be received when performing an update on a contact object. The contact ID in the poll message represents the contact object that was updated. A "paResult" of "1" indicates a successful update.

 

<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="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T11:21:00.086+02:00</epp:qDate>
      <epp:msg>Contact 'myContactID' Update Successful</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <contact:panData>
        <contact:id paResult="1">myContactID</contact:id>
        <contact:paTRID>
          <epp:clTRID>CLTRID-13028592426-DUKR</epp:clTRID>
          <epp:svTRID>ZACR-EPP-12F58765CB2-116CA</epp:svTRID>
        </contact:paTRID>
        <contact:paDate>2011-04-15T09:20:59Z</contact:paDate>
      </contact:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028592638-BZ9V</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F5876A0B4-14CF7</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>


Address Information Cannot Be Empty

Attempting to completely remove required contact information by effectively "blanking" the record in both "loc" and "int" postal info types is not allowed. A "paResult" of "0" indicates a failure in the contact object update.

<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="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ  >
      <epp:qDate>2011-04-15T11:13:37.230Z</epp:qDate>
      <epp:msg>2306: Contact address information Name and City elements cannot be empty</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <contact:panData>
        <contact:id paResult="0">myContactID</contact:id>
        <contact:paTRID>
          <epp:clTRID>ZACR-EPP-137DB3F80E9-5AFAD</epp:clTRID>
          <epp:svTRID>ZACR-EPP-137DB3F80E9-19460</epp:svTRID>
        </contact:paTRID>
        <contact:paDate>2011-04-15T11:13:37Z</contact:paDate>
      </contact:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13394134723-6PAR</epp:clTRID>
      <epp:svTRID>ZACR-EPP-137DB3FBFCC-3EE95</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 


Domain Poll Messages

 

Nameserver Associated Messages

All ZA policies perform nameserver checks on the initial registration of a domain as well well as on any update of nameservers. In doing this, there are several messages that will be queued for a registrar regarding nameservers. The following messages may appear in a registrar's message queue:

1. "2306: Authoritative Nameserver failure for domain 'exampledomain.test.dnservices.co.za': Timeout from 'A.B.C.D'" means that the nameserver with IP address A.B.C.D is unreachable by the registry for verification of authority against the domain name. Please ensure that the nameserver is authoritative and that the incoming IP addresses of the registry are allowed to query the nameserver. The registry will reperform automatic checks on the nameservers every hour for 1 consecutive week for new registrations.

2. "Warning: Nameserver failure for suspended domain 'exampledomain.test.dnservices.co.za'" means that the registry has attempted to verify the nameservers specified at the time of registration of the domain, for 7 consecutive days. After 7 days, the registry will stop checking the nameservers and keep the domain suspended. Please issue a domain update to include authoritative nameservers.

3. "Nameserver check successful for 'exampledomain.test.dnservices.co.za'" means that the nameservers specified on the registration of a new domain name have been identified as authoritative. Having received this message, the domain name will be unsuspended and published in the next zone update.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id=ABC-123">
      <epp:qDate>2011-04-15T10:56:16.634Z</epp:qDate>
      <epp:msg>[MESSAGE AS ABOVE]</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13365609602-JWKW</epp:clTRID>
          <epp:svTRID>ZACR-EPP-137313DC2DB-80DC7</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T10:56:16Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13365610070-EMUX</epp:clTRID>
      <epp:svTRID>ZACR-EPP-137313E0278-CCFCE</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

General Domain Update Successful

A message similar to the one below will be queued when a pending update on a domain was successful.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T11:26:06.873+02:00</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' update successful</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13028595657-CM6N</epp:clTRID>
          <epp:svTRID>ZACR-EPP-12F587B4B0B-52C2</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T09:26:06Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028596231-7JZK</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F587B4F18-66CB0</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>


Domain Auto-Renew

If a domain has expired and the autorenew flag is set to "True", the domain will be automatically renewed for an additional year if funds are available.
The simplest way to identify that a domain has been renewed through the auto-renew is by the "<epp:svTRID>" tag which will have the prefix of "AR_REPLY" .
The poll message below will be queued for a domain that has been renewed due to auto-renew.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
 xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2013-04-15T09:29:20.050Z</epp:qDate>
      <epp:msg>Domain Renew Command completed successfully</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:renData>
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:exDate>2013-04-15T09:17:46Z</domain:exDate>
      </domain:renData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>AR-13375922251-385307</epp:clTRID>
          <epp:svTRID>AR_REPLY-13375922251-246939</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2013-04-15T09:29:19Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13375926070-HJSO</epp:clTRID>
      <epp:svTRID>ZACR-EPP-1376EBAB8F0-7645E</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>




Domain Delete Successful


When a domain name has reached the end of the Deletion Process, a message indicating its deletion and removal from the zone will be queued.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T09:45:26.400Z</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' Deletion Successful</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13357790902-6SFL</epp:clTRID>
          <epp:svTRID>ZACR-EPP-13702A35F50-5C3D5</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T09:45:26Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13357857660-FGU8</epp:clTRID>
      <epp:svTRID>ZACR-EPP-13702A3EC7D-5EEE1</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

 
Domain Delete Within Grace Period


If a domain is deleted within the grace period, the message below will be queued at the end of the Grace Period when the domain is released back into the pool of available names.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T10:12:33.075Z</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' Grace Period Deletion Successful</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13367311330-6VUI</epp:clTRID>
          <epp:svTRID>ZACR-EPP-1373B6264A1-BE139</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T10:12:31Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13367312148-D8LL</epp:clTRID>
      <epp:svTRID>ZACR-EPP-1373B62B22C-2BCAF</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

Domain Delete Due to Expiry

1. If a domain has expired and the Autorenew flag is set to false, the domain will enter Auto-Delete and the Pending Suspension Phase.

2. If after 5 days the domain has not been renewed, the domain will enter the Pending Deletion Phase and the action as listed below will be "PendingDeletion"

The following poll message will be queued if a domain enters the Deletion Process due to expiry.

 

 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T12:50:16.125Z</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' Expired; action 'PendingSuspension' pending in 5 days</epp:msg>
    </epp:msgQ>
    <epp:trID>
      <epp:clTRID>CLTRID-13357902299-IHTX</epp:clTRID>
      <epp:svTRID>DNS-EPP-137034D23BC-CDB9E</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 


Request Canceled By Another Process

 

The message below is received when an update was attempted, but the update was cancelled before it could be applied. Updates can be cancelled due to transfers, renewals, or the issuing of a Cancel Pending Action request. For the example below the pending update action will be 'PendingSuspension'. The message is sent to the registrar who successfully cancelled the pending update.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ>
      <epp:qDate>2011-04-15T14:18:05.020+02:00</epp:qDate>
      <epp:msg>Request 'PendingSuspension' canceled by another process</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13028698173-6SKT</domain:clTRID>
          <epp:svTRID>ZACR-EPP-12F5917B808-71191</domain:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T12:18:04Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028699303-HAJQ</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F5918C05A-50596</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 


Transfer Request

 

The message below is received when a transfer request is issued for a domain. The Registrar of Record will receive the message.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T14:36:27.549+02:00</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' transfer requested by 'RegistrarID',
a decision is required to approve or reject the transfer</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:trnData>
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:trStatus>pending</domain:trStatus>
        <domain:reID>RegistrarID</domain:reID>
        <domain:reDate>2011-04-15T12:36:27Z</domain:reDate>
        <domain:acID>CurrentID</domain:acID>
        <domain:acDate>2011-04-15T12:37:47Z</domain:acDate>
      </domain:trnData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028710879-4AIN</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F5929931B-BAEC8</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 


Domain Transfer Successful

 

Message to New Registrar of Record

 

The message below is received when a transfer of a domain has been successful. The message is received by the new Registrar of Record of the domain.

 

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T14:36:50.275+02:00</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' transfer successful</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:trnData>
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:trStatus>clientApproved</domain:trStatus>
        <domain:reID>RegistrarID</domain:reID>
        <domain:reDate>2011-04-15T12:36:50Z</domain:reDate>
        <domain:acID>CurrentID</domain:acID>
        <domain:acDate>2011-04-15T12:36:50Z</domain:acDate>
      </domain:trnData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13025163365-EBGK</epp:clTRID>
          <epp:svTRID>ZACR-EPP-12F440607EA-1C274</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T12:36:50Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13028710892-9TSI</epp:clTRID>
      <epp:svTRID>ZACR-EPP-12F5929EBE1-9EC72</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

 
Message to Old Registrar of Record
 
 
The message below will be queued to the old Registrar of Record when a transfer has been completed:

 
 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-05-01T10:17:53.073Z</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservices.co.za' transferred away</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:trnData>
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:trStatus>clientApproved</domain:trStatus>
        <domain:reID>RegistrarID</domain:reID>
        <domain:reDate>2011-05-01T10:17:18Z</domain:reDate>
        <domain:acID>CurrentID</domain:acID>
        <domain:acDate>2011-05-01T10:17:48Z</domain:acDate>
      </domain:trnData>
      <domain:panData>
        <domain:name paResult="1">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>ZACR-EPP-13F663CF3DC-B6243</epp:clTRID>
          <epp:svTRID>ZACR-EPP-13F663CF3DC-E6DC3</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-05-01T10:17:52Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13718098980-7SEV</epp:clTRID>
      <epp:svTRID>ZACR-EPP-13F663D7CAD-D972</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

Transfer Rejected


Message to Requesting Registrar

If a transfer for a domain was not successful, the requesting registrar will receive the following poll message:

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-05-01T10:29:45.032Z</epp:qDate>
      <epp:msg>2106: Domain 'exampledomain.test.dnservices.co.za' transfer rejected</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:trnData>
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:trStatus>clientRejected</domain:trStatus>
        <domain:reID>RegistrarID</domain:reID>
        <domain:reDate>2011-05-01T10:29:03Z</domain:reDate>
        <domain:acID>CurrentID</domain:acID>
        <domain:acDate>2011-05-01T10:29:42Z</domain:acDate>
      </domain:trnData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>ZACR-EPP-13F6647B675-F0955</epp:clTRID>
          <epp:svTRID>ZACR-EPP-13F6647B675-24B5C</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-05-01T10:29:44Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13718106034-EGDJ</epp:clTRID>
      <epp:svTRID>ZACR-EPP-13F664859C2-1277</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>


Message to Registrar of Record

If a transfer for a domain was not successful, the Registrar of Record will receive the following poll message:

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2014-08-14T11:44:24.385Z</epp:qDate>
      <epp:msg>2106: Domain 'exampledomain.test.dnservices.co.za' retained</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:trnData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
        <domain:name>exampledomain.test.dnservices.co.za</domain:name>
        <domain:trStatus>clientRejected</domain:trStatus>
        <domain:reID>RequestingRarID</domain:reID>
        <domain:reDate>2014-08-14T11:43:12Z</domain:reDate>
        <domain:acID>CurrentRarID</domain:acID>
        <domain:acDate>2014-08-14T11:44:12Z</domain:acDate>
    </domain:trnData>
      <domain:panData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>ZACR-EPP-147D4542DCC-4DDB6</epp:clTRID>
          <epp:svTRID>ZACR-EPP-147D4542DCC-4269A</epp:svTRID>
      </domain:paTRID>
        <domain:paDate>2014-08-14T11:44:24Z</domain:paDate>
    </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:svTRID>ZACR-EPP-147D455473F-E9833</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>




Domain Update While in Transfer Phase


In this scenario, a transfer request for the domain was issued. While the domain was still in the Transfer process, an update was performed on the domain.

The Transfer period was allowed to exire. Upon expiration of the Transfer period, the update on the domain was still outstanding.

The domain was transfered and the update that was outstanding was cancelled.


The update will also get cancelled if the transfer request is processed via the registrant e-mail voting.

The losing registrar that performed the update during the transfer process will receive the poll message below:
 
<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T09:35:25.543Z</epp:qDate>
      <epp:msg>Request 'PendingUpdate' canceled by another process</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13348281108-HYKK</epp:clTRID>
          <epp:svTRID>ZACR-EPP-136C9F4941B-F3F7E</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T09:35:25Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13348281596-BF2M</epp:clTRID>
      <epp:svTRID>ZACR-EPP-136C9F4CD5C-4E193</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 


Domain Transfer While in Update Phase

In this scenario an update was performed on a domain. During the update, a transfer request was sent for the domain.

The update for the domain was executed prior to the transfer being approved.

When this happens, the transfer is cancelled to allow for the review of the change prior to another transfer decision being made.

The poll message below will be queued:

 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T07:09:38.055Z</epp:qDate>
      <epp:msg>Request 'PendingTransferUpdate' canceled by another process</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13348193658-IBEV</epp:clTRID>
          <epp:svTRID>ZACR-EPP-136C96F2404-500EC</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T07:09:37Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13348194070-6D4G</epp:clTRID>
      <epp:svTRID>ZACR-EPP-136C96F5384-E4BB6</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>



Domain Transfer While in Deletion Phase

In this scenario a domain is in the Deletion phase. While in the Deletion phase, a transfer request is sent for the domain.

The transfer is processed prior to the domain being deleted via registrant voting.
 
If the domain goes past the suspension phase and enters the final deletion phase, the request "PendingDeletion" will be canceled.

The result is that the domain is not deleted, but transfered to the requesting registrar.

The losing registrar will receive the following poll message:

 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T08:37:55.175Z</epp:qDate>
      <epp:msg>Request 'PendingSuspension' canceled by another process</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">sexampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13348246518-5QCK</epp:clTRID>
          <epp:svTRID>ZACR-EPP-136C9BFCC56-180F1</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T08:37:55Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13348247140-15K6</epp:clTRID>
      <epp:svTRID>ZACR-EPP-136C9C02764-61265</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>



Domain Delete With New Dependancy

In this scenario a domain exists with 2 subordinate hosts. The domain is deleted and enters the Deletion Phase.

While in the Deletion Phase, a new domain is created, relying on the subordinate hosts of the deleting domain.

This means that the currently deleting domain cannot be deleted as the newly created domain uses the deleting domain's subordinate hosts..

The domain will exit its deletion phase, and a poll message as follows will be returned:

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    <epp:msgQ count="1" id="ABC-123">
          <epp:qDate>2011-04-20T08:34:25.065Z</epp:qDate>
      <epp:msg>2305: Unable to delete domain 'exampledomain.test.dnservices.co.za'
  as new dependencies exist</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13349106187-45NX</epp:clTRID>
          <epp:svTRID>ZACR-EPP-136CEDF8CA9-4D73A</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-20T08:34:24Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13349109348-46QB</epp:clTRID>
      <epp:svTRID>ZACR-EPP-136CEE34EA5-DE8BD</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

Cancel Domain Deletion With No Funds

The message below will only be queued if:
  1. A domain has the Autorenew Flag set to "True"
  2. The registrar has insufficient funds in their account
  3. The domain expires and is triggered for suspension
  4. The registrar attempts to cancel either the "PendingSuspension" or "PendingDeletion" actions
 
If the registrar has no funds available and attempts to cancel the deletion of a domain that has entered the Deletion Phase through Autorenew, the message below will be queued upon attempt to cancel the deletion.

<epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
  xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
    </epp:msgQ count="1" id="ABC-123">
      <epp:qDate>2011-04-15T12:22:02.774Z</epp:qDate>
      <epp:msg>2104: Insufficent funds to process cancel pending action
                             that results in a domain renewal.</epp:msg>
    </epp:msgQ>
    <epp:resData>
      <domain:panData>
        <domain:name paResult="0">exampledomain.test.dnservices.co.za</domain:name>
        <domain:paTRID>
          <epp:clTRID>CLTRID-13388989203-C4VK</epp:clTRID>
          <epp:svTRID>ZACR-EPP-137BC983399-CBE3C</epp:svTRID>
        </domain:paTRID>
        <domain:paDate>2011-04-15T12:22:02Z</domain:paDate>
      </domain:panData>
    </epp:resData>
    <epp:trID>
      <epp:clTRID>CLTRID-13388992746-D2RV</epp:clTRID>
      <epp:svTRID>ZACR-EPP-137BC983D10-71FEC</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>


Domain Entered Closed Redemption
 

The following poll message will be queued when a domain has entered Closed Redemption.

 <epp:epp xmlns:epp="urn:ietf:params:xml:ns:epp-1.0">
  <epp:response>
    <epp:result code="1301">
      <epp:msg>Command completed successfully; ack to dequeue</epp:msg>
    </epp:result>
      <epp:qDate>2012-11-05T04:55:52.551Z</epp:qDate>
      <epp:msg>Domain 'exampledomain.test.dnservicesco.za' in Closed Redemption</epp:msg>
    </epp:msgQ count="1" id="ABC-123">
    <epp:trID>
      <epp:clTRID>CLTRID-13545992394-8G8U</epp:clTRID>
      <epp:svTRID>ZACR-EPP-13B644529E5-7C5FA</epp:svTRID>
    </epp:trID>
  </epp:response>
</epp:epp>

 

Last update: 27-05-2015 04:26:56

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.

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