Guidelines

• Attempts to modify a domain name that is not on your tag will count towards the limit set for abuse detection. Full details of the limits and how they affect you are given in our acceptable use policy.

Instructions

• Send to the address applications@nic.uk.
  
• Use a subject line of TAG MODIFY (replace TAG with your tag name in capital letters).
  
• Use the 'key' field to specify a domain name, followed by the fields you wish to change; see the  template below.
• Make sure the email is PGP-signed with a registered PGP key.

Operation template

operation: modify
key:
account-id:
dns0-id:
dns0:
dns1-id:
dns1:
dns2-id:
dns2:
dns3-id:
dns3:
dns4-id:
dns4:
dns5-id:
dns5:
dns6-id:
dns6:
dns7-id:
dns7:
dns8-id:
dns8:
dns9-id:
dns9:
trad-name:
type:
co-no:
opt-out:
addr:
locality:
city:
county:
postcode:
country:
b-addr:
b-locality:
b-city:
b-county:
b-postcode:
b-country:
a1-id:
a1-name:
a1-phone:
a1-fax:
a1-mobile:
a1-email:
a2-id:
a2-name:
a2-phone:
a2-fax:
a2-mobile:
a2-email:
a3-id:
a3-name:
a3-phone:
a3-fax:
a3-mobile:
a3-email:
b1-id:
b1-name:
b1-phone:
b1-fax:
b1-mobile:
b1-email:
b2-id:
b2-name:
b2-phone:
b2-fax:
b2-mobile:
b2-email:
b3-id:
b3-name:
b3-phone:
b3-fax:
b3-mobile:
b3-email:
first-bill:
recur-bill:
auto-bill:
next-bill:
notes:
renew-not-required:

Notes

1. The 'account-name' field is not included in this list, because the account name, (i.e. the registrant of the domain name), cannot be modified by the registrar. For further details see the registrant transfer process.
2. The 'account-id' field may be specified to move a domain name to another account. This operation will only succeed if the new account has the same account-name and is on your tag.
3. The 'key' must be specified as this determines which domain is to be modified.
4. Nameserver, contact and account objects can be modified directly using nameserver MODIFY, contact MODIFY and account MODIFY operations respectively.
   
5. All of the same restrictions with registrant types apply as with the Request operation.
6. Account fields (including contacts on the account) will modify the account object directly, affecting all domain names on the account.
7. The renew-not-required field may only be set by this operation, taking a value of 'Y'. This field can only be unset through sending a renewal request for the domain.

Nameservers

1. The nameserver fields in a MODIFY operation affect only the specified domain.
2. The 'dns-id' fields link the domain name to the specified nameserver objects.
   
3. Existing nameserver objects cannot be changed by a MODIFY. The effect of 'dns' fields depends on your configuration options: If your nameserver consolidation option is set to 'Off', the Automaton will create a new nameserver object and link it to the domain. If your nameserver consolidation option is set to 'On', the Automaton will first attempt to link the domain to an existing nameserver with the same dns name and glue records, creating a new nameserver if no match is found.
   
4. Specifiying nameservers using 'dns0'..'dns9' or 'dns0-id'..'dns9-id' will overwrite the entire list of nameservers for that domain name.
5. The id's of any newly-created nameservers will be returned by the Automaton in the reply e-mail.
   

Contacts

1. Each account can link to a maximum of 6 contact objects, comprising between 1 and 3 admin contacts (a1, a2, a3) and up to 3 billing contacts (b1, b2, b3). Each contact occupies one slot in the account. Contacts cannot be shared between accounts.
2. For each of the six slots in the account there are fields for the corresponding contact fields: 'name', 'email', 'phone', 'fax' and 'mobile'. These fields will directly alter any existing contact object in the given slot. If the account currently has no contact in the corresponding slot, a new contact object will be created.
3. The id's of any newly-created contacts will be returned by the Automaton in the reply e-mail.
   
4. Contact 'id' fields link an existing contact to the given slot in the parent account. To empty a slot, set either the contact id or contact name field to 'NULL' - this will not alter the contact object.
5. 'Orphaned' contacts with no remaining links to the account remain in the register and can be linked at a later time.
6. If a contact has been linked twice to an account (e.g. as a2 and b1) then any changes made to one slot (e.g. a2) will also affect the other (b1). If a MODIFY operation makes separate changes to both slots, the Automaton will attempt to apply both sets of changes to the same contact object - the order in which they are applied is not guaranteed in this specific case.
7. Contacts store three types of telephone number - 'phone', 'fax' and 'mobile' - with up to 10 numbers of each type. Using a field (e.g. 'a1-fax') one or more times will over-write all existing numbers of that type.
8. See Contact Overview for more details.

Reply template

When a domain name is successfully modified, the reply from the automaton looks like this:

Subject: Re: ACK TAG 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 delegation for automaton-example.co.uk has been updated successfully.
To check the current state of the entry for automaton-example.co.uk
in the database, use the following command

% whois -h whois.nic.uk automaton-example.co.uk

Regards

Nominet

Notes

1. 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.

operation: modify
key: example.co.uk
dns0-id: NS100001
dns1: ns2.somewhere-new.co.uk
dns2: ns1.example.co.uk 1.1.1.1

The following identifiers were created as part of your Modify:
Nameserver ns2.somewhere-new.co.uk.: NS100004
Nameserver ns1.example.co.uk.: NS100005

The following identifiers were created as part of your Modify:
Nameserver ns2.somewhere-new.co.uk.: NS100004

operation: modify
key: example.co.uk
a1-name: Miss Green
a1-phone: 01234 567890
a1-phone: 02345 678901
a1-fax: NULL
a2-name: Mrs White
a2-email: white@test.co.uk
b2-id: C123456

The following identifiers were created as part of your registration:
Additional Admin Contact (Mrs White): C345678