Skip to content



Reassign the Domain Name Record to a new Holder.


Only the Managing AR of a Domain Name Record can submit a Reassign Domain Request.


The Reassign process is comprised of two Registration Actions: Delete Domain and Create Domain –executed one after the other as a single atomic Registration Action,ensuring that no other Create Domain Requests for the Domain are processed in between.

Upon the completion of the Reassign Domain Request, a new Domain Name Record is created, with the submitting AR as the Managing AR, for one Registration Period starting the date the reassignment is processed.

IMPORTANT – no information is inherited from the previous Domain Name Record. Where continuity of operation of the Domain Name is required, the DNS Information blocks from the previous Domain Name Record MUST be specifically included in the Reassign Request.

Code Example

The Reassign request is very similar to the Create Domain Request. The difference is in the tags identifying the request type (namely, the <update> and <reassign> tags).

<?xml version="1.0" encoding="UTF-8"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd isocil-1.0.xsd
urn:ietf:params:xml:ns:domain-1.0 domain-1.0.xsd isocil-domainrequest-1.0.xsd
urn:ietf:params:xml:ns:contact-1.0 contact-1.0.xsd">
                        <domain:hostAddr ip="v4"></domain:hostAddr>
                        <domain:hostAddr ip="v6">::b:0:1</domain:hostAddr>
                <domain:contact type="admin">MH16016-IL</domain:contact>
                <domain:contact type="tech">NEW2</domain:contact>
                <domain:contact type="zone">MH16016-IL</domain:contact>
                <domain:period unit="y">2</domain:period>
                        <contact:postalInfo type="int">
                            <contact:name>Israel Israeli</contact:name>
                            <contact:org>Some Organization</contact:org>
                                <contact:street>12 Herzel St. </contact:street>
                                <contact:sp> </contact:sp>
                        <contact:voice>+972 2 3512811</contact:voice>
                        <contact:fax>+972 2 3512811</contact:fax>
                        <contact:postalInfo type="int">
                            <contact:name>Israel Israeli</contact:name>
                            <contact:org>Some Company Ltd.</contact:org>
                                <contact:street>12 Herzl St.</contact:street>
                                <contact:city>Beer Sheva</contact:city>
                        <contact:voice>+1 4 3560890</contact:voice>
                        <contact:fax>+1 8 3567789</contact:fax>
            <secDNS:create xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1">


  • <domain:reassign> ... </domain:reassign>: Defines that the desired Registration Action, Reassign a Domain, where:
    • <domain:name> ... </domain:name>: Defines the Domain Name to be Reassigned.
    • <domain:ns> ... </domain:ns>: Defines a DNS Information block, where <domain:hostAttr> ...</domain:hostAttr> defines the details of one DNS server:
      • <domain:hostName> ... </domain:hostname>: contains the DNS server's name.
      • <domain:hostAddr> ... </domain:hostAddr>: contains the DNS server's IP address. The <domain: hostAddr> tag attribute "ip" – defines the IP version, which is one of the following:
        • "v4" – for IPV4 address
        • "v6" – for IPV6 address. More information can be found at RFC5732.
    • <domain:registrant> ... </domain:registrant>: Contains the Reference Label to the Extension Block, where the Regsitrant's details are listed.
    • <domain:contact> ... </domain:contact>: Contains either an already existing Contact Object Handle (managed by the submitting AR), or a Reference Label to the Extension Block where the contact's details are listed. The tag attribute "type" – defines the Contact's Role, which is one of the following:
      • "admin" – Administrative Contact.
      • "tech" – Technical Contact.
      • "zone" – Zone Contact.
    • <domain:locktransfer> ... </domain:locktransfer>: Controlling the Lock Transfer option. (see sec. 6.1(h)). above)
    • <domain:period ...> ... </domain:period>: The registration period requested, up to and including the Maximal Registration Period, expressed in Registration Units.
  • <isocil:ext>...</isocil:ext>: Defines the IL Extension Block.
  • <isocil:contact>...</isocil:contact>: A Contact Object creation block.
    • <contact:id>...</contact:id>: Contains a Reference Label declared in the Standard EPP Block.
    • <contact:type>...</contact:type>: Contains one of the following:
      • "registrant" – to indicate that the details are of the Registrant (a Domain Name Record Attribute).
      • "domain" – to indicate that the details are of a Contact Object.
  • <contact:postalInfo>...</contact:postalInfo>: Contains a block defining the Contact's details. The Tag attribute type="int" should be included as specified in the example.
    • <contact:name>...</contact:name>: Contains the Contact's full name. In case of a person, name and surname separated by a space. In case of a legal-entity, e.g, a company, the company's full name, including appropriate suffix, e.g., "Ltd." – separated by spaces.
    • <contact:org>...</contact:org>: Contains the Contact's organization.
    • <contact:addr>...</contact:addr>: A block containing the postal information associated with the Contact:
      • <contact:street>...<contact:street> Contains the street and number of the Contact's address.
      • <contact:city>...</contact:city> Contact's city.
      • <contact:sp>...</contact:sp> Contact's State/Province.
      • <contact:pc>...</contact:pc> Contact's postal code.
      • <contact:cc>...</contact:cc> Contact's two-letter country code, according to ISO-3166.
    • <contact:voice>...</contact:voice>: Contact's telephone number, in the following format: "+[country code] [area code] [phone number]"
    • <contact:fax>...</contact:fax>: Contact's facsimile number, in the following format: "+[country code] [area code] [phone number]"
    • <contact:email>...</contact:email>: Contact's direct mail address.
  • <secDNS:create>...</secDNS:create>: A DNSSEC object creation block.
    • <secDNS:dsData>...</secDNS:dsData>: Contains all Delegation Signer (DS) record elements of the domain. DNS name must be defined. Information about the DS resource record can be found at RFC4034 section 5.1. For detailed requirements please check DS Specifications
      • <secDNS:keyTag>...</secDNS:keyTag> The key tag of the DNSKEY RR referred to by the DS record.
      • <secDNS:alg>...</secDNS:alg> The algorithm number of the DNSKEY RR referred to by the DS record.
      • <secDNS:digestType>...</secDNS:digestType> The Digest Type field identifies the algorithm used to construct the digest.
      • <secDNS:digest>...</secDNS:digest> The DS record refers to a DNSKEY RR by including a digest of that DNSKEY RR.
      • <secDNS:keyData>...</secDNS:keyData> OPTIONAL. DNSKEY info. Information about the DNSKEY resource record can be found at RFC4034 section 2.1.
        • <secDNS:flags>...</ secDNS:flags> Zone Key flag.
        • <secDNS:protocol>...</secDNS:protocol> Protocol field. Must be 3.
        • <secDNS:alg>...</secDNS:alg> Algorithm use to determine the format of the Public Key field.
        • <secDNS:pubKey>...</secDNS:pubKey> The Public Key Field holds the public key material.

Tags occurrence table

Tag Occurrences
Size + Remarks
<epp> 1
<command> 1
<update> 1
<domain:reassign> 1
<domain:name> 1 Token: 9-73.
<domain:ns> 1 Token.
<domain:hostAttr> 0-13
<domain:hostname> Token: 1-100.
<domain:hostAddr> Obligatory when Glue record needed.
<domain:contact type="admin"> 1
<domain:contact type="tech"> 1
<domain:contact type="zone"> 1
<extension> 1
<domain:locktransfer> 0-1
<domain:period> 1
<isocil:ext> 1
<isocil:create> 1
<isocil:contact> 1-4 All subtags but: <contact:org> <contact:sp> <contact:pc> <contact:voice> <contact:fax> are mandatory.
<contact:type> Registrant contact type obligatory.
<secDNS:create> 1
<secDNS:dsData> 1-6 All subtags but: <secDNS:keyData> are mandatory
<secDNS:keyData> 1 All subtags are mandatory.
<clTRID> 1 token: 3-64