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 zero to ten elements which may be either of the following:
  • <ns:create> containing the sub-elements of a nameserver object to be created and used.
  • <domain:nsObj> containing the identifier of an existing nameserver object to be used. If an empty <domain:ns> element is given then all nameservers will be removed from the domain name. The individual elements (name, addr) of a nameserver object cannot be modified via a domain update command.
• 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.

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-1.0"
             xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
             nom-domain-1.0.xsd">
             <domain:name>example.co.uk</domain:name>
             <domain:account>
              <account:update
               xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-1.0"
               xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0">
               <account:contact type="admin" order="1">
                <contact:update>
                  <contact:email>admin@strant.co.uk</contact:email>
                </contact:update>
               </account:contact>
              </account:update>
             </domain:account>
             <domain:ns
              xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0">
              <ns:create>
             <ns:name>ns2.example1.co.uk</ns:name>
           </ns:create>
          <domain:nsObj>NS1001</domain:nsObj>
        </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.
• Removing the billing address.
• Adding a billing address where one did not exist.
• 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 six account:contact elements. This element has two attributes - type which may be "admin" or "billing" 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" or "billing". The billing address is removed if a blank contact is provided. If a billing address is provided and one does not already exist then a new address is added. Otherwise fields are modified. 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. A billing contact is removed from the account object and the billing address is also removed. The first admin contact is modified.

    <?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-1.0"
          xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0"
          xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-account-1.0
           nom-account-1.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:addr type="billing"/>
           <account:contact type="admin">
             <contact:create>
               <contact:name>Ms S. Strant</contact:name>
               <contact:phone>01865 123457</contact:phone>
               <contact:fax>01865 123456</contact:fax>
               <contact:email>s.strant@strant.co.uk</contact:email>
             </contact:create>
           </account:contact>
           <account:contact type="billing">
           </account:contact>
           <account:contact type="admin">
             <contact:update>
               <contact:phone>01865 232564</contact:phone>
             </contact:update>
           </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:fax>
• <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-1.0"
            xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-contact-1.0
            nom-contact-1.0.xsd">
             <contact:roid>C11001</contact:roid>
             <contact:fax/>
             <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

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

Note that modifying a nameserver object will automatically modify all domain names associated with it.

<ns:update> element

The <ns:update> element contains the following sub-elements:

• A <ns:roid> element containing the identifier of the nameserver object to be modified.
• An optional <ns:name> element giving the new name for the nameserver object.
• An optional <ns:addr> element with ip attribute of "v4" giving the new ipv4 address for the nameserver object.
• An optional <ns:addr> element with ip attribute of "v6" giving the new ipv6 address for the nameserver object.
  

Example of a nameserver 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>
         <ns:update
          xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0"
          xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-ns-1.0
          nom-ns-1.0.xsd">
           <ns:roid>NS1001</ns:roid>
           <ns:name>ns0.example2.co.uk</ns:name>
         </ns:update>
       </update>
       <clTRID>ABC-12345</clTRID>
     </command>
   </epp>

Example of a successful nameserver 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>