The contact MODIFY operation is used to make changes to the register after the initial registration.
Instructions
- Send to the address applications@nic.uk.
- Use a subject line of TAG contact MODIFY.
- Use the 'contact-id' field to specify a contact, followed by the fields that you wish to change; see the template below.
Operation template
operation: modify
contact-id:
name:
email:
phone:
fax:
mobile:
Notes
- The 'contact-id' field must be specified as this determines which contact is to be modified.
- This will alter the contact object directly, irrespective of how it may be used by its parent domains or account. All domains on the account will reflect the changes.
- Contacts store three types of telephone number - 'phone', 'fax' and 'mobile' - with up to 10 numbers of each type. Using a field (e.g. 'fax') one or more times will over-write all existing numbers of that type.
- The contents of the 'phone', 'fax' and 'mobile' fields can be removed by setting the value to 'NULL'. The contents of the 'name' and 'email' fields cannot be removed; setting them to 'NULL' will result in an error message.
- See Contact Overview for more details.
Reply template
When a contact is modified successfully, the following template is used:
Subject: Re: ACK TAG Contact Modify
Your message has been processed by the UK NIC automated DNS
delegation system. The required additions/changes have been
made to the database and will become visible in the zone file within
thirty minutes.
The application to modify the contact object with id Cxxxxxx below
has been processed successfully.
Regards
Nominet
Your original message follows
--------------------------------------------------------------------------------------
....
Notes
- The TAG in the subject lines is replaced with your TAG, provided that you specified it in the original subject.
Errors
After processing your operation the Automaton sends an automated reply. If there is a problem with the operation then two different error conditions may occur
- non-fatal errors (warning messages) may be appended to successful replies.
- fatal errors that prevent the operation from being carried out; an error reply is generated.
Full details of the template of the error reply and the meaning of the error messages can be found
here.
Examples
Consider a contact object whose state before the operation is:
- id: C123456
- name: Mr Brown
- email: email@test.co.uk
- phone:
- fax: 09876 543210
- mobile: 07111 111111
- mobile: 07222 222222
The following request is then sent to the Automaton:
operation: modify
contact-id: C123456
name: Miss Green
phone: 01234 567890
fax: NULL
mobile: 07333 333333
This request alters the contact with id 'C123456'; it sets the name to 'Miss Green', leaves the email field unaltered, changes the phone field to '01234 567890', clears the contents of the fax field, and replaces the mobile fields with '07333 333333'. The state of the contact after the operation is then:
- id: C123456
- name: Miss Green
- email: email@test.co.uk
- phone: 01234 567890
- fax:
- mobile: 07333 333333