The EPP update command allows you to modify the attributes of a domain, account, nameserver or contact object.

Domains

In order to modify the attributes of a domain name, the update command must contain a <domain:update> element that identifies the domain namespace and location of the domain schema.

<domain:update> element

The domain:update element contains the following child elements:

• A <domain:name> element.
• An optional <domain:account> element containing an <account:update> element with account attributes to be modified. This is described below. Note that modifying account attributes will affect any other domain names that are associated with that account.
• An optional <domain:ns> element which contains the nameservers in order for the domain name after the modification. This contains one to ten elements containing a <domain:host> sub-element with the following child elements:
  • A <domain:hostName> element giving the name of the host object. 
  • Optional <domain:hostAddr> elements giving the ip addresses of the host object. This element should be provided only if the nameserver needs glue records. It should have an "ip" attribute of "v4" or "v6" indicating the ip version. A maximum of one ipv4 and one ipv6 address can be provided.
• An optional <domain:first-bill> element.
  
• An optional <domain:recur-bill> element.
  
• An optional <domain:auto-bill> or <domain:next-bill> element. Only one of these two elements should be present.
  
• An optional <domain:purchase-order> element.
  
• An optional <domain:notes> element.
• An optional <domain:renew-not-required> element. Note that this is only available in the 1.2 versions of the nom- schemas.

Example of a domain:update command

<?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.nominet.org.uk/epp/xml/nom-domain-2.0"
       xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-2.0
       nom-domain-2.0.xsd">
       <domain:name>example.co.uk</domain:name>
       <domain:account>
        <account:update
         xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-2.0"
         xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-2.0">
         <account:contact order="1">
          <contact:update>
           <contact:email>admin@strant.co.uk</contact:email>
          </contact:update>
         </account:contact>
        </account:update>
       </domain:account>
       <domain:ns>
        <domain:host>
          <domain:hostName>ns0.epp-example.com</domain:hostName>
        </domain:host>
        <domain:host>
         <domain:hostName>ns0.epp-example.co.uk</domain:hostName>
         <domain:hostAddr ip="v4">111.123.145.121</domain:hostAddr>
         <domain:hostAddr ip="v6">abcd::1234</domain:hostAddr>
        </domain:host>
       </domain:ns>
       <domain:auto-bill/>
       <domain:next-bill>5</domain:next-bill>
      </domain:update>
     </update>
     <clTRID>ABC-12345</clTRID>
   </command>
 </epp>

Example of a successful domain:update response

<?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="1000">
       <msg>Command completed successfully</msg>
     </result>
     <trID>
       <clTRID>ABC-12345</clTRID>
       <svTRID>123456</svTRID>
     </trID>
   </response>
 </epp>

Accounts

The EPP update command allows you to modify the attributes of an account object. You can modify an account object in one of the following ways: 

• Modifying one of the account fields (trad-name, type, co-no, opt-out). This includes modifying a field that was previously empty and deleting a field.
• Modifying an existing address. When this is done all address fields that are to be modified must be provided including those that are to be deleted.
• Modifying one of the main contacts.
• Modifying one of the non-main contacts. In order to do this, the contact identifier must be provided.
• Removing a contact (not the main admin contact).
• Adding a contact (not the main admin contact).
  

account:update element

The update command must contain an account:update element that identifies the account namespace and location of the account schema. This element contains the following child elements:

• An <account:roid> element to contain the identifier of the account object to be modified. (Note this may be omitted when the account:update element sits inside a domain:update element).
• An optional <account:trad-name> element.
• An optional <account:type> element.
• An optional <account:co-no> element.
• An optional <account:opt-out> element.
• Up to three account:contact elements. This element has two attributes - type which must be "admin" and order which may be "1", "2" or "3". The account:contact contains one of the following sub-elements:
  • <contact:create>. The contact given here is added to the account. The <contact:create> element is described in the Domain create section.
  • <contact:update>. The contact fields given by the sub-elements are modified. The <contact:update> element is described below.
  • An empty account:contact element will empty that contact slot, leaving the contact in the register for future use.
• Up to two <account:addr> elements with a type attribute of "admin". The <account:addr> element will have the following sub-elements:
  • <account:street>
  • <account:locality>
  • <account:city>
  • <account:county>
  • <account:postcode>
  • <account:country>
    

Example of an account:update command

This modifies the trad-name, type and co-no of an account object, and adds an admin contact.

<?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>
       <account:update
        xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-2.0"
        xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-2.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-account-2.0
        nom-account-2.0.xsd">
         <account:roid>286467</account:roid>
         <account:trad-name>R. S. Industries</account:trad-name>
         <account:type>STRA</account:type>
         <account:co-no>NI123456</account:co-no>
         <account:contact>
           <contact:create>
             <contact:name>Ms S. Strant</contact:name>
             <contact:phone>01865 123457</contact:phone>
             <contact:email>s.strant@strant.co.uk</contact:email>
           </contact:create>
         </account:contact>
       </account:update>
     </update>
     <clTRID>ABC-12345</clTRID>
   </command>
 </epp>

Example of a successful account:update response

    <?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="1000">
            <msg>Command completed successfully</msg>
          </result>
          <trID>
            <clTRID>ABC-12345</clTRID>
            <svTRID>65789465</svTRID>
          </trID>
        </response>
      </epp>

Contacts

In order to modify the attributes of a contact object, the update command must contain a contact:update element that identifies the contact namespace and location of the contact schema.

<contact:update> element

• A <contact:roid> element to contain the identifier of the contact object to be modified.
• <contact:name>
• <contact:phone>
• <contact:mobile>
• <contact:email>
  

Example of a contact:update command

<?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>
       <contact:update
        xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-2.0"
        xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-contact-2.0
        nom-contact-2.0.xsd">
         <contact:roid>C11001</contact:roid>
         <contact:email>contact@example.co.uk</contact:email>
       </contact:update>
     </update>
     <clTRID>ABC-12345</clTRID>
   </command>
 </epp>

Example of a successful contact:update response

    <?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="1000">
            <msg>Command completed successfully</msg>
          </result>
          <trID>
            <clTRID>ABC-12345</clTRID>
            <svTRID>65789465</svTRID>
          </trID>
        </response>
      </epp>

Nameservers

• Modify the name field
• Modify the ipv4 field
• Modify the ipv6 field