Domain Delete

The syntax for this command follows standard EPP Domain name mapping, RFC-5731 and is not extended. Note that our business process implies a bit different semantics for delete operation.

<domain:delete> command is used to discontinue registrar management of a domain name (.lv domain objects are never really deleted from the registry, they only expire and become available for new registrations).

Note

<domain:delete> request is refused for newly registered domains before they are included in a bill.

On “deleting”, the following things happen:

  • registrar, billing and technical contact roles are removed from a domain (registrant is given a chance to take over management of the domain name for a few days - during that period, a domain name is not available for new registrations);
    • as a consequence, from that moment, a domain name becomes “invisible” from the EPP viewpoint: further EPP requests for it would respond that "Domain name is outside of EPP scope";
  • network information is removed - domain is taken out of the zone;
  • the domain is still active and available to domain holder until it expires;
  • the domain is on hold for 30 days and is “deleted” on the 30th.

We suggest You to learn more about clientAutoRenewProhibited state.

If <domain:delete> is called while a domain name is in a pendingRenew state (for a domain name, included in the actual bill), the command is not performed immediately but the domain name is marked with a clientAutoRenewProhibited status - to be discontinued when the bill is finalized (on the last day of the month).

Client request

The only relevant parameter is domain:name:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
  <command>
    <delete>
      <domain:delete
       xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
       xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd">
       <domain:name>do-not-like-that-domain-anymore.lv</domain:name>
      </domain:delete>
    </delete>
    <clTRID>mFvZwyJKYHYmWpgS2JlG</clTRID>
  </command>
</epp>

Server response

  • On successful refusal of the registrar’s role, the server will respond with a code of 1000 (“Command completed successfully”)
  • When domain name is in a pendingRenew state, response code would be 1001 (“Command completed successfully; action pending”)

Registrar role cannot be refused for a domain name which is in a pendingDelete, pendingCreate, pendingTransfer or deleteProhibited status (set either by client or server) then:

  • error response code would be 2304 (“Object status prohibits delete operation”).

    Note

    The command may fail with such a response also if delete command was called on a domain name which expires in the current month (and therefore, would be included in this month’s bill) before the bill has been generated (during the first few days of the month).

Response example for a successful request (refusing domain, included in the current bill):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">

  <response>
    <result code="1001">
      <msg>Domain name do-not-like-that-domain-anymore.lv marked as AFTER PAYMENT DO NOT RENEW</msg>
    </result>
    <trID>
      <clTRID>mFvZwyJKYHYmWpgS2JlG</clTRID>
      <svTRID>LVNIC-20110627-b8c49f5859f20d81640f9dfc94771136-7</svTRID>
    </trID>
  </response>
</epp>

Example of error response (domain still in a pendingCreate state):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">

  <response>
    <result code="2304">
      <msg>Domain status prohibits delete operation</msg>
    </result>
    <trID>
      <clTRID>mFvZwyJKYHYmWpgS2JlG</clTRID>
      <svTRID>LVNIC-20110627-b8c49f5859f20d81640f9dfc94771136-7</svTRID>
    </trID>
  </response>
</epp>