If there is an issue with a command or an operation submitted to one of our domain management tools, you will receive an error message. There are several types of error messages that you may receive:
| Error Code | Description | |
|---|---|---|
| V000 | Subject Line not of the form 'TAG Action' | The subject line for each Automaton request must consist of both the current registrar tag and the action to be performed. Details of the correct subject line can be found in the documentation for each operation. |
| V001 | Subject Line contains unknown action | The Automaton checks each message's subject line to determine what action to take with the request. 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. | The tag you have used is not currently active. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information. |
| 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 either do not include the 'key' field or a value within it. |
| V009 | Domain <xxx> cannot be requested via this automaton | Our systems will only accept requests for .uk domains under our defined second levels. This error will occur if you request a domain that we either do not administer or includes an additional prefix such as 'www.'. |
| V010 | Domains with two letters are not allowed | Third level domains under co.uk, me.uk, net.uk and org.uk cannot consist of two letters. For further information please see clause 5.6 of our registration rules. |
| V011 | Domains with one character are not allowed | Third level domains under co.uk, me.uk, net.uk and org.uk cannot consist of just one character. For further information please see clause 5.5 of our registration rules. |
| V012 | Fully-qualified domain names must be no longer than <xxx> characters | The maximum length of a registration up to and including .uk is 64 characters. For further information please see clause 5.7 of our registration rules. |
| V013 | The account name field cannot be modified | Changes to an account name can only be made by a registrant transfer or by our support staff in the case of minor corrections. |
| V014 | The tag '<xxx>' has been barred from creating or retagging domains. | The tag used is currently barred from performing this action. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information. |
| V015 | The tag '<xxx>' has been barred. | The tag used is currently barred from performing any actions. Please contact our Member and Registrar Support team on +44 (0)1865 332233 for further information. |
| V016 | The tag '<xxx>' is unrecognised | This error occurs when an invalid tag is used in the 'registrar-tag' field, often due to the tag not being provided in capital letters. |
| V017 | bad value for `first-bill' field (must be either `th' or `bc') | The 'first-bill' field can only be set to either 'th' or 'bc' ('NULL' to clear). |
| V018 | bad value for `recur-bill' field (must be either `th' or `bc') | The 'recur-bill' field can only be set to either 'th' or 'bc' ('NULL' to clear). |
| V019 | Missing account name | The 'account-name' field is mandatory when creating a new account. It specifies whom the account is registered for and cannot be modified by the registrar at a later date. |
| V020 | Missing or invalid account identifier | Operations relating to a specific account must include the account-id number. |
| V023 | Error Reading Nameserver <xxx> | This error occurs when invalid information or characters are provided in the name server details. |
| V024 | Missing glue record for server <xxx> | When a name server is provided that is the child of the domain supplied in the request, it is necessary to create a glue record by including its IP address. |
| V025 | Bad IP address for server <xxx> : <xxx> | An IP address will be treated as invalid if it: Starts with 0, 10, 127, 192.168. Starts within 172.16 to 172.32. Ends with 0 or 255. |
| V027 | Bad value for `type' (must be one of LTD, PLC, PTNR, LLP, STRA, IND, OTHER, FCORP, FOTHER, RCHAR) | Please see our registrant types page for full details regarding the 'type' field. |
| 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> | Postcodes are validated to verify that they are formatted correctly. If you follow the postcode guidelines from GovTalk, the postcode should be accepted. |
| V030 | <xxx> field is too long (<xxx> is maximum) | Most fields have a limit of 200 characters, the exceptions being: 'co-no' up to 50 characters. 'addr' up to 8 lines of 256 characters. 'b-addr' up to 8 lines of 256 characters. 'notes' up to 15 lines of 256 characters. |
| V036 | Too many nameservers specified (10 is maximum) | You can only provide a maximum of 10 name servers for a registration. |
| V040 | Bad month '<xxx>' specified for list action (Must be of form CCYY-MM) | The format of the month field must be Year-Month, for example March 2007 is 2007-03. |
| V042 | Invalid month '<xxx>' in list action | The format of the month field must be Year-Month, for example March 2007 is 2007-03. |
| V044 | Unrecognised PGP format | The most common reason for this error is sending an automaton request in MIME/HTML format. This causes a duplicate message to be sent in the Automaton request. This error can also happen when:
|
| V045 | Error occurred during PGP decode | This error can be caused by a corruption of the PGP signature or the surrounding ASCII armor lines, these being: -----BEGIN PGP SIGNED MESSAGE----- -----BEGIN PGP SIGNATURE---- -----END PGP SIGNATURE---- This may be due to the wrong method being used when signing the message, errors copying the message to an email after generation, or by the email client modifying the message. If using PGP 9 or above, please also check that the Hash algorithm is set to SHA-1. The hash setting should be displayed at the top of a signed message and can changed within the PGP program by double clicking on your key and selecting edit from the hash drop down menu. |
| 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 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 | The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page. |
| V050 | Key has been disabled | The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page. |
| V051 | Key has expired | The PGP key used to sign the message is no longer valid. Details on how to add a new key can be found on our PGP registration page. |
| V052 | Signature has a timestamp in the future | The Automaton compares the current time with time found in the sender’s PGP timestamp. The error will occur if the timestamp is more than five minutes fast. In most cases this issue can 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 | Duplicate name servers cannot be provided for the same registration. |
| V055 | You may not retag to NOMINET. | The NOMINET tag is reserved for situations where a host has name servers but does not have a tag. This change can only be made directly by us at the request of the registrant. |
| V056 | Multiple Key Fields found | Only one key field can be stated for most requests. To submit multiple requests in an email to the Automaton the request must be provided in full; separated from the previous request by a blank line. |
| V057 | Invalid field '<xxx>' for <xxx> operation | Occurs if a field name is not valid for the stated operation. This is very commonly caused by the field name starting with a capital letter. |
| V058 | This Request will have no effect | The request does not contain any information to act upon. Often this is caused by lines being ignored due to incorrect field names or a problem with their formatting such as the use of capital letters. |
| V060 | Message contained no requests | Occurs if no fields are present in a request after any invalid text has been removed. |
| V061 | Nameserver '<xxx>' appears to be an IP address | An IP address can accompany the name server's host name in cases where a glue record is required, but our systems do not allow the IP address to be provided on its own. |
| V063 | Multiple Instances of Field '<xxx>' found | This error will occur if a field, other than 'addr', 'b-addr' or 'notes', is used more than once in a single request. |
| V064 | ISO 3166 Country Code required for <xxx> country. | The mandatory value for 'country' or the 'b-country' fields has been omitted. For a list of valid two-letter 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, GG, JE or IM are used in the 'country' or 'b-country' fields. |
| V069 | '<xxx>' field missing or empty | No data has been provided for a mandatory field in a registration request. |
| V070 | Missing admin address | No data has been provided for the mandatory 'addr' address field in a registration request. |
| V071 | Missing admin contact | No data has been provided for the mandatory primary administrative contact in a registration request |
| V073 | Invalid Company Number | For registrations where the LTD or PLC registrant types are used, the company number provided must consist of one or more numbers, and may be preceded by SC, NI, FC, BR, SF or NF. For registrations where the LLP registrant type is used, the company number provided must consist of one or more numbers, and may be preceded by LP, NL, SO, OC or SL. For registrations where the SCH registrant type is used, the DfES school number provided must consist of seven numbers. For English school numbers, you should also separate the third digit from the fourth with a hyphen. |
| V074 | Company Number required for UK Limited and Public Limited Companies | For registrations where the LTD or PLC registrant types are used, the company number provided in the 'co-no' field must consist or one or more numbers, possibly preceded by SC, NI, FC, BR, SF or NF. |
| V076 | Only 100 requests permitted in a single email | A maximum of 100 requests can be submitted to the Automaton in a single PGP signed email. Mass modifications can also be made using the Automaton’s bulk operation. |
| V077 | Company Number required for LLP reg-types | For registrations where the LLP registrant type is used, the company number provided in the 'co-no' field must consist or one or more numbers, possibly preceded by LP, NL, SO, OC or SL. |
| V078 | School Number required for schools | For registrations where the SCH registrant type is used, the DfES school number provided in the 'co-no' field must consist of seven numbers. For English school numbers, you should also separate the third digit from the fourth with a hyphen. |
| V079 | Company Number not required for <xxx> reg-types | No information should be provided in the 'co-no' field unless the registrant type listed in the 'type' field is LTD, PLC, LLP, SCH, RCHAR. |
| V080 | The 'co-no' field cannot be modified for an sch.uk domain name | Please contact our support department to inform us of any update to a school's DfES number. |
| V081 | Reg type must be LTD for .ltd.uk domain name | The registrant type 'LTD' must be set in the 'type' field when making a ltd.uk domain registration. |
| V082 | Reg type must be PLC for .plc.uk domain name | The registrant type 'PLC' must be set in the 'type' field when making a plc.uk domain registration. |
| V083 | Invalid 'opt-out' field | The 'opt-out' field can only be set to either 'y' or 'n' ('NULL' to clear). |
| 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. | Only individuals may opt-out of having their address details listed in the WHOIS. The setting can only be made if the registrant type in the 'type' field is set to be 'IND' for UK individuals or 'FIND' for non UK individuals. |
| V085 | Only individuals may opt-out of having their address details listed in the public register. | Only individuals may opt-out of having their address details listed in the WHOIS. The setting can only be made if the registrant type in the 'type' field is set to be 'IND' for UK individuals or 'FIND' for non UK individuals. |
| V086 | Contents of field <xxx> cannot be removed | This occurs if an attempt is made to remove the contents of a field that is either mandatory or required by other existing fields. |
| 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. | This request would cause you to exceed your advised credit limit and any tags associated with your account are now suspended until further payments have been received. Therefore, you are no longer able to make any new registrations or renewals. Please contact our Member and Registrar Support team on +44 (0)1865 332233 as a matter of urgency to place an amount of money on your account or log on to your online account to pay any overdue invoices. |
| V089 | Incorrect PGP constructs | The Automaton expects 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 that 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 that is either not on your tag or 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. | Domain names can only be cancelled 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 due to a Nominet process:<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 | |
| V213 | Length of %s must not exceed %s. | |
| V217 | DNS data out of sequence. | |
| V230 | Enumber range invalid | The lastE164Number provided is smaller than the E164Number. |
| V231 | <xxx> format invalid | A date specified has not been provided in RFC 3339 format. |
| V232 | Execution date is in the future | The execution date on the ENUM token is in the future. |
| V233 | Expiration date is in the past | The expiration date on the ENUM token provided is in the past, it is advisable that you contact your validation agency to resolve this. |
| V234 | RegistrarID in token is different to user | Occurs if a registrar sends a create when the tag specified upon login differs from the tag specified in the registrarID of the token. |
| V235 | <xxx> invalid | Invalid number provided for E164Number or LastE164Number, for example if the number is too long or starts with a non-UK prefix. |
| V236 | Enumber not on your tag. | Occurs if a request is made to modify or renew a registration if not on your tag and without a valid token. |
| V237 | Enumber has already been renewed. | Occurs if a renew operation would not increase the expiry date by at least one day. |
| V238 | Token is older than the current one | This is returned when the ENUM token provided has an older execution date than the current one stored. |
| V239 | Part or all of Enumber range exists. | Occurs if a create command fails due to it overlapping with an existing registration. |
| V240 | <xxx> in token is different to one provided out. | This applies to E164Number and lastE164Number fields given within the ENUM token and is returned when the fields in the token don't match provided fields outside of the token. |
| V241 | Token expires before registration | Occurs in a create operation where the expiry date of the token is less than a year in the future, or in a modify where a new token does not cover the remaining registration period. |
| V245 | Domain name %s exists already. | |
| V261 | PGP signature expired. | |
| V262 | Bad renew-not-required field. | |
| V263 | Renew-not-required field can only be unset by renewal of the domain. | |
| V264 | No more than 100 renewal reversals are permitted in a single request. | |
| V265 | The following domains are in a state which prevents any previous renewal from being undone: | |
| V266 | The account-id %ld does not correspond to a valid registrant account. | |
| V267 | A destination account-id may not be specified for this case. | |
| V268 | The destination account name does not match that of the domains associated with case %ld. | |
| V269 | No matches found on your tag for bulk operation. | |
| V270 | Renewals cannot be undone more than once within the same registration period. | |
| V271 | Auto-bill/next-bill cannot be set (positively) with the renew-not-required parameter. | |
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