5.7.1. Update domain

A domain update command is used to alter details of a domain.

The domain update command is an update element in the domain namespace (http://www.nic.cz/xml/epp/domain-1.4).

The command must be contained in the <update> command type.

5.7.1.1. Command element structure

The <domain:update> element must declare the domain namespace and schema and it must contain the following child elements:

  • <domain:name> (1) – the domain name as eppcom:labelType,

  • <domain:add> (0..1) – a list of contact handles that will be added to the list of administration contacts of this domain:

  • <domain:rem> (0..1) – a list of contact handles that will be removed from the list of administration contacts of this domain:

  • <domain:chg> (0..1) – the new values of domain attributes that will be changed by this update. Omitted attributes will remain unchanged.

    • <domain:nsset> (0..1) – change the domain’s nsset by its handle as fredcom:objIDChgType; if the element is empty, the current nsset will be unlinked from the domain,

    • <domain:keyset> (0..1) – change the domain’s keyset by its handle as fredcom:objIDChgType; if the element is empty, the current keyset will be unlinked from the domain,

    • <domain:registrant> (0..1) – change the domain’s registrant by its handle as fredcom:objIDType,

    • <domain:authInfo> (0..1) – change the domain’s authorization information (AuthInfo) as fredcom:authInfoType.

Important

Since FRED 2.48.0, server can be configured so that the AuthInfo must meet some basic requirements, such as minimum length (which can be configured).

[registry]
# Minimal length of authinfo
authinfo_length_min = 8

Calling update object with empty AuthInfo leads to removal of all object AuthInfos.

Example
<?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>
      <update>
         <domain:update xmlns:domain="http://www.nic.cz/xml/epp/domain-1.4"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/domain-1.4 domain-1.4.5.xsd">
            <domain:name>mydomain.cz</domain:name>
            <domain:add>
               <domain:admin>CID-ADMIN2</domain:admin>
            </domain:add>
            <domain:rem>
               <domain:admin>CID-ADMIN1</domain:admin>
            </domain:rem>
            <domain:chg>
               <!-- do nothing with nsset (absent element) ~ NULL -->
               <!-- remove keyset ~ empty string -->
               <domain:keyset/>
               <!-- change registrant -->
               <domain:registrant>CID-MYOWN</domain:registrant>
            </domain:chg>
         </domain:update>
      </update>
      <clTRID>uafh003#17-07-18at10:45:41</clTRID>
   </command>
</epp>
FRED-client equivalent
> update_domain mydomain.cz CID-ADMIN2 CID-ADMIN1 () (NULL '' CID-MYOWN)

5.7.1.1.1. ENUM extension

The <domain:update> element is used in the same way as described above.

The command extension can be used to change the validation of an ENUM domain and/or its publish flag.

The command’s <extension> element must contain a single <enumval:update> element which declares the enumval namespace (http://www.nic.cz/xml/epp/enumval-1.2) and schema and contains:

  • <enumval:valExDate> (0..1) – a new validation expiration date as xs:date; the new date must be within range – see the explanation in RenewDomain,

  • <enumval:publish> (0..1) – a new setting for publishing the ENUM domain in a public directory as xs:boolean; true – display, false – hide.

Example
<?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>
      <update>
         <domain:update xmlns:domain="http://www.nic.cz/xml/epp/domain-1.4"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/domain-1.4 domain-1.4.5.xsd">
            <domain:name>1.1.1.7.4.5.2.2.2.0.2.4.e164.arpa</domain:name>
         </domain:update>
      </update>
      <extension>
         <enumval:update xmlns:enumval="http://www.nic.cz/xml/epp/enumval-1.2"
          xsi:schemaLocation="http://www.nic.cz/xml/epp/enumval-1.2 enumval-1.2.0.xsd">
            <enumval:chg>
               <enumval:valExDate>2018-01-02</enumval:valExDate>
            </enumval:chg>
         </enumval:update>
      </extension>
      <clTRID>cant003#17-07-18at10:49:42</clTRID>
   </command>
</epp>
FRED-client equivalent
> update_domain 1.1.1.7.4.5.2.2.2.0.2.4.e164.arpa () () () () 2018-01-02

5.7.1.2. Response element structure

The FRED EPP server responds with a plain result message which does not contain any response data (no <resData>).

See also Success or failure of a command.

5.7.1.2.1. ENUM extension

Response extension is not used in reply to this command.