After processing your request the Automaton will send an automated reply. If there is a problem then two different error conditions may occur:
| Error Code | Description | |
|---|---|---|
| V000 | Subject Line not of the form 'TAG Action' | |
| V001 | Subject Line contains unknown action | The Automaton checks the subject line to determine what action to take with the message. If this does not correspond to one of the possible actions it returns this error. Details of the correct subject line can be found in the documentation for each operation. |
| V002 | Nominet have notified you that any further applications to register new domain names will be refused. | |
| V007 | Unknown field '<xxx>' | A template is given for each of the Automaton requests in the documentation for the operation type. Any fields given which do not appear in the template will not be recognised and will cause the Automaton to abandon processing the request with this error. |
| V008 | No Domain name given | This error occurs if you perform an operation on a domain, such as renew, but do not include the 'key' field or a value within the 'key' field. |
| V009 | Domain <xxx> cannot be requested via this automaton | This error occurs if you request a domain that Nominet does not administer. You may only request second level .uk domains though Nominet systems. This error will also occur if you include 'www.' in your domain request. |
| V010 | Domains with two letters are not allowed | |
| V011 | Domains with one character are not allowed | |
| V012 | Fully-qualified domain names must be no longer than <xxx> characters | |
| V013 | The account name field cannot be modified | |
| V014 | The tag '<xxx>' has been barred from creating or retagging domains. | |
| V015 | The tag '<xxx>' has been barred. | |
| V016 | The tag '<xxx>' is unrecognised | This error occurs when an invalid tag is used in the 'registrar-tag' field. This most commonly occurs if the tag used in the 'registrar-tag' field is not all in capital letters. |
| V017 | bad value for `first-bill' field (must be either `th' or `bc') | |
| V018 | bad value for `recur-bill' field (must be either `th' or `bc') | |
| V019 | Missing account name | |
| V020 | Missing or invalid account identifier | |
| V023 | Error Reading Nameserver <xxx> | |
| V024 | Missing glue record for server <xxx> | |
| V025 | Bad IP address for server <xxx> : <xxx> | |
| V027 | Bad value for 'reg-type' (must be one of LTD, PLC, PTNR, LLP, STRA, IND, OTHER, FCORP, FOTHER, RCHAR) | |
| V028 | Invalid country code for <xxx> (must be the two-letter ISO 3166 country code) | The country code used in the 'country' or 'b-country' fields must be a valid two-letter country code from ISO 3166. |
| V029 | Invalid postcode: <xxx> | The Automaton validates postcodes to verify they are in a valid format. If you follow the postcode guidelines from GovTalk, the Automaton should accept the postcode. |
| V030 | <xxx> field is too long (<xxx> is maximum) | |
| V036 | Too many nameservers specified (10 is maximum) | |
| V040 | Bad month '<xxx>' specified for list action (Must be of form CCYY-MM) | |
| V042 | Invalid month '<xxx>' in list action | Month must be of the format YYYY-MM. |
| V044 | Unrecognised PGP format | The most common cause of this error is sending the request in MIME/HTML format. This causes a duplicate message to be sent in the Automaton request. This error can also be caused when:
|
| V045 | Error occurred during PGP decode | This error is caused by either a corruption of the PGP signature itself or the ASCII armor lines that surround the message. The ASCII armor lines being: -----BEGIN PGP SIGNED MESSAGE----- -----BEGIN PGP SIGNATURE---- -----END PGP SIGNATURE---- This can be caused by the wrong method being used when PGP signing the message, an error copying the message to an email after generation, or by the email client modifying the message. Also, in PGP version 9 or above, the Hash should be set to SHA1. |
| V046 | Message not in Clear Text Signed Format | This error occurs when the message received by the Automaton has either been encrypted or has not been PGP signed. |
| V047 | Signing Key not recognised | This error occurs where the key used to sign the request has not been registered with our system, it is therefore not possible to determine either the validity of the message or the requestor’s identity. Details on how to add a new key can be found on our PGP registration page. You may also receive this error if you sign an Automaton request with a PGP key recently added to our system. The Automaton's key update occurs daily around 8pm (GMT). |
| V048 | Signature did not match the text | This error can occur for a number of reasons and things to watch out for are:
|
| V049 | Key has been revoked | |
| V050 | Key has been disabled | |
| V051 | Key has expired | |
| V052 | Signature has a timestamp in the future | The Automaton compares the current time with the message sender’s time found in the PGP timestamp, the error will occur if the timestamp is more than 5 minutes fast. This can usually be resolved by correcting the system time, date and time zone of the computer used to PGP sign the message. |
| V053 | Duplicate Nameserver found in list | |
| V055 | You may not retag to NOMINET. | |
| V056 | Multiple Key Fields found | |
| V057 | Invalid field '<xxx>' for <xxx> operation | |
| V058 | This Request will have no effect | |
| V060 | Message contained no requests | |
| V061 | Nameserver '<xxx>' appears to be an IP address | |
| V063 | Multiple Instances of Field '<xxx>' found | This error will occur if a field is used more than once in a single Automaton request. |
| V064 | ISO 3166 Country Code required for <xxx> country. | This error will occur if a mandatory value for 'country' or the 'b-country' fields has been omitted. For a list of allowable country codes, please refer to ISO 3166. |
| V065 | postcode required for GB, GG, JE and IM Country codes for <xxx> address | The 'postcode' and 'b-postcode' fields are mandatory if the country codes GB, JE, GG or IM are used in the 'country' or 'b-country' fields. |
| V069 | '<xxx>' field missing or empty | |
| V070 | Missing admin address | |
| V071 | Missing admin contact | |
| V073 | Invalid Company Number | |
| V074 | Company Number required for UK Limited and Public Limited Companies | |
| V076 | Only 100 requests permitted in a single email | |
| V077 | Company Number required for LLP reg-types | |
| V078 | School Number required for schools | |
| V079 | Company Number not required for <xxx> reg-types | |
| V080 | The 'reg-co-no' field cannot be modified for an sch.uk domain name | |
| V081 | Reg type must be LTD for .ltd.uk domain name | |
| V082 | Reg type must be PLC for .plc.uk domain name | |
| V083 | Invalid 'reg-opt-out' field | |
| V084 | No registrant type is specified for this registration. The registrant type must be specified either as a UK individual ('IND') or non-UK individual ('FIND') before the registrant may be permitted to opt-out of having their address details listed in the public register. | |
| V085 | Only individuals may opt-out of having their address details listed in the public register. | To opt-out of having an address listed in the WHOIS, the registrant type in the 'type' field must be set to UK Individual or Non UK Individual. |
| V086 | Contents of field <xxx> cannot be removed | |
| V087 | Contacts cannot be removed and edited at the same time. | A contact name has been set to NULL and another contact field set. |
| V088 | You have exceeded your advised credit limit and any tags associated with your account are now suspended until further payments have been received. You are still able to detag domain names which are due for renewal and update nameserver information but you cannot make any new registrations. Please contact your Credit Controller as a matter of urgency to place an amount of money on your account or to pay any overdue invoices. | |
| V089 | Incorrect PGP constructs | We expect a single instance of each of the three PGP construct lines. This error can occur if your message is sent in MIME/HTML format or if there is an attachment in your message. |
| V094 | Domain name exists already | This error occurs if you attempt to register a domain which is already registered. |
| V096 | Domain name is not registered to your tag | This error will occur if you attempt to make changes to a domain which is not on your tag or is not registered. |
| V101 | Domain names cannot be detagged in the first month of registration. If you wish to cancel this domain name please refer to http://www.nominet.org.uk/go/automaton - "Cancelling a Registration" | |
| V102 | Domain name not registered in the last 2 years. | Cancellations can only be made in the first registration period. |
| V103 | Domain name is in legal dispute | |
| V105 | Current and registering tag different. | Domain names cannot be cancelled if there has been a registrar change. |
| V107 | Tag missing from subject line | |
| V108 | Tag in subject line does not match PGP signatory. | |
| V109 | Invalid bulk operation. | |
| V110 | Field '<xxx>' cannot be modified using a bulk modification query. | |
| V113 | Old nserver must be non-blank for bulk n-server replacement. | |
| V114 | Nserver replacements and update bulk requests are not-compatible | |
| V115 | Glue record required for nameserver <xxx> | |
| V116 | Field <xxx> appears more than once in update clause for bulk request. | |
| V117 | Field <xxx> empty | |
| V120 | Invalid date field <xxx> | |
| V121 | Invalid tag field | |
| V122 | You cannot filter by tag | |
| V123 | It has been detected that you have submitted more than 1000 requests for already registered names in the last 24 hours. You will be blocked for 24 hours. | |
| V124 | You have been blocked from using the automaton | This error occurs if you have exceeded the acceptable use limits for registering domains which already exist. |
| V127 | Domain names may not begin xn-- | |
| V128 | Domain name is not within its renewal period or cannot be renewed. | A domain name can only be positively renewed up to 6 months in advance of the expiry date. This message will be returned if you send a positive renewal request outside of this 6 month period. This error can also occur due to a number of Nominet processes, including:
If you have questions about this, please contact our Member and Registrar Support Team. |
| V129 | Domain names may not be renewed when recur-bill is set to 'bc' | When the recur-bill field is set to 'bc', it indicates that you wish Nominet to bill the registrant directly. In order to positively renew a domain name the recur-bill field needs to be set to 'th'. |
| V133 | <xxx> address must have either city of (locality and country) fields present | |
| V134 | Bad value for <xxx> field (must be between 0 and 182) | The auto-bill field is used to indicate how many days before expiry you wish to renew a domain name. You can set an auto-bill field on a domain name with a value between 1 and 182 where the value indicates the number of days before expiry that a domain name will be renewed. |
| V138 | Domain name contravenes naming rules | |
| V140 | '<xxx>' field may not currently be changed | This error will occur when either a modify or bulk operation updating the auto-bill or next-bill fields cannot be processed for all the domain names requested. For the bulk operation, the domain names that cannot be processed are listed. There are three reasons why the operation would fail for a particular domain name:
|
| V141 | Account <xxx> does not exist | |
| V142 | Account <xxx> is not on your tag | |
| V143 | Nameserver <xxx> does not exist | |
| V144 | Nameserver <xxx> is not on your tag | |
| V145 | <xxx> may not be set retrospectively | This error can occur if you attempt to set the auto-bill or next-bill fields to a date in the past. The value in these fields must be a date in the future. If the expiry date has passed but you wish to renew the domain name, then you can submit a renewal request. |
| V146 | Contact <xxx> does not exist | |
| V147 | Contact <xxx> is not on your tag | |
| V148 | Both in-line and ? objects present. | |
| V149 | Bad IPV6 address for server <xxx> : <xxx> | |
| V150 | Domain name labels must not be longer than 63 characters | |
| V151 | Domain name has been paid for | |
| V154 | Invalid registrant identifier <xxx> | |
| V156 | Domain name has already been renewed. | |
| V157 | Auto-bill and next-bill cannot both be set. | |
| V158 | operation: field does not match subject | This error occurs if the operation in the subject line of the email and the 'operation' field do not match. This error can also occur if you use capital letters in the 'operation' field. |
| V159 | Signature has a timestamp more than 3 days in the past | The Automaton compares the current time with the message sender’s time found in the PGP timestamp. The error will occur if the timestamp is more than 72 hours slow. This can usually be resolved by correcting the system time, date and time zone of the computer used to PGP sign the message. |
| V166 | More than one ipv<xxx> address given for name-server | |
| V169 | Missing 'operation' field | |
| V171 | Name server is more than 255 characters | |
| V172 | Name server <xxx> is invalid - label has invalid length | |
| V173 | Name server <xxx> is invalid | |
| V174 | Domain name has been renewed, but not yet paid for. | This error is generated because a previous renewal request has already been processed and accepted. Renewal invoices are generated on the 8th of the month following that in which we accept the renewal request. If the renewal invoice goes past its 30 days credit terms, the expiry date for the domain name will revert to its previous state and we will advise the registrant that the renewal process has not been completed. Attempts to resend the renewal request will result in this error until we receive the renewal payment. Please note, we always advise the registrant to contact you about the renewal of the domain name, however they may pay us directly. As soon as we receive payment for the outstanding renewal fees, the renewal date for the domain name will be updated accordingly. You can view and pay any outstanding invoices on your credit account by logging into your online service account. If you have any further problems with this error message, your credit account or payments to us, please contact our member and registrar support team on +44 (0) 1865 332233 or email support@nominet.org.uk. |
| V175 | It has been detected that you have exceeded usage limits for cancellations. | |
| V177 | Field <xxx> is no longer allowable | This error occurs if you have used a field which is no longer used by the Automaton. Please refer to our field definitions for a list of allowable fields. |
| V178 | next-bill or auto-bill cannot be set when recur-bill is 'bc' | |
| V180 | You must accept or reject the registrar change authorisation request | This error occurs if an invalid response is given to a registrar change authorisation request. Please refer to the registrar change authorisation request for possible valid responses. |
| V181 | You cannot accept or reject the registrar change case-id <xxx> | You have tried to accept a case-id that doesn't exist or has expired. |
| V182 | Attempt to 'like' a numeric field. | You have tried to do a bulk 'like' filter using account-id, auto-bill or next-bill. |
| V184 | Missing identifier for contact modification | |
| V185 | Missing identifier for account modification | |
| V186 | Missing identifier for nameserver modification | |
| V187 | Unable to have no main billing contact when there are other billing contacts | |
| V188 | You cannot transfer to the account <xxx> | The domain names on the account are not on your tag. |
| V189 | Account names do not match for the following domain names: | |
| V190 | Invalid operation <xxx>: <xxx> | |
| V191 | Invalid ID prefix '<xxx>', expecting '<xxx>' | An invalid contact, nameserver or account identifier has been provided. |
| V192 | Reference <xxx> made to non-existant contact | |
| V193 | Contact has both data and external reference <xxx> | |
| V194 | Operation blocked by Nominet process | This request cannot be made due to a Nominet process. This can occur for a number of reasons, including:
If you have questions about this, please contact our Member and Registrar Support Team. |
| V195 | The following domain names may not be released:<xxx> | The listed domain names cannot be released due to other processes on them. |
| V196 | Invalid registrar change case <xxx> | |
| V197 | Tag <xxx> do not accept registrar changes | |
| V198 | Account <xxx> is not on tag <xxx> | |
| V199 | A target account may not be provided for an account release | |
| V200 | Contact <xxx> is not on account <xxx>. | |
| V201 | Too many lines in request: Maximum is 500 | |
| V202 | Cannot have multiple admin contacts with id <xxx>. | |
| V203 | Cannot have multiple billing contacts with id <xxx>. | |
| V204 | Cannot change registrar-tag with modify operation; use release operation instead. | |
| V205 | Too many <xxx> numbers in request: Maximum is 10 | |
| V206 | Invalid ID suffix <xxx>, expecting '-UK'. | |
| V207 | The following domains do not have account names that match that of the account specified:<xxx> | |
| V208 | The following domains are not registered to the tag given:<xxx> | |
| V209 | The set of domain names given could not be modified. | |
| V210 | Period format is invalid | |
| V211 | Period is outside acceptable range | |
Subject: Re: ERROR
[Received_subject] The following error occurred while
processing your DNS auto delegation
[Error_code Error_message]
If you have any questions please contact nominet@nominet.org.uk.
Documentation on the automaton can be found on the Nominet UK Web
site at http://www.nic.uk/
Your original message follows
-------------------------------------------------------------------------------
[Original_message]
| Error | Description |
|---|---|
| Deprecated field <xxx> found; this field has been ignored | A deprecated field has been used which does not do anything and so has been ignored. |
| Deprecated field <xxx> found; this field has been processed anyway. | A deprecated field has been used which is a synonym for a current field and has been used as such. |
| You are within <xxx>% of your credit limit. The calculation takes into account your current outstanding balance, plus any new registrations and renewals which have been made during the current month. If you anticipate that you will exceed your current credit limit before you make your next payment, please contact your Credit Controller to place an amount of money on your account or to pay any overdue invoices. This will avoid the suspension of your tag(s). | Returned when the registrar is within 25% of their credit limit. |
| Tag in Subject <xxx> ignored - PGP signatory <xxx> used instead | The tag given in the subject line does not match that of the PGP signature. |
| Text outside of the PGP armoury was ignored | There was some text in the original operation that was outside of the PGP armoury (the area that is signed by PGP). This text was ignored. |
| Reg-type set to LTD | This is done if we have an operation for a .ltd.uk domain name and reg-type is not set in the request. |
| Reg-type set to PLC | This is done if we have an operation for a .plc.uk domain name and reg-type is not set in the request. |
| Tag in email body <xxx> ignored - PGP signatory <xxx> used instead. | This is if an 'ips-key' field is included in an operation and it does not match the tag taken from the PGP signature. |
If a non-fatal error occurs then a section will be appended to the reply template below explaining what these errors were. An example of such a section is as follows
Note that the following NON-FATAL errors occurred
during the processing of the request
Text outside of the PGP armoury was ignored