This article provides answers to common error messages in the Robot.
In order to be able to use the Robot your browser needs to be configured to accept cookies.
On submitting an order everything seems to be ok, but nothing happens (confirmation emails, entry under domains/CHProv (KK) orders)!
Most likely an invalid email address has been registered under
Master data ->
Email addresses at the
Robot order confirmation address. A valid email address needs to be entered here for the Robot to function properly.
Handles are always tied to the respective domain ending (TLD). For exmpl, only .de handles can be used for .de domains.
The last column of the handle list (Menu item
Handles) specifies which roles you can use the handle for. H stands for holder, A for admin-c, T for tech-c and Z for zone-c.
Company handles can only be used as holder (except for .at). All other roles (admin-c, tech-c and zone-c) require a person handle.
To be able to use a .de handle for a particular role, the following optional fields should be completed:
- Admin-c: Phone and email
- Tech-c: Phone, fax and email
- Zone-c: Phone, fax and email
An example of such an error message:
--- status: failed transaction: RO20110726111619-018731200-167488 message: - text: Illegal operation on own domain. argument: your-server.de level: error code: 399 reference: 167488
The domain is already hosted by Hetzner, so a domain transfer cannot be started. A Hetzner internal domain transfer is needed for the domain.
This error message usually occurs with .com/.net/.org/.info/.biz domains. An example of such an error message:
--- status: Object status prohibits operation. code: failed transaction: RO20110804191323-007996000-168158 reference: 168158
This message means that a transfer block has been placed on the particular domain concerned (
clientTransferProhibited or similar). This can be checked via a whois query for example.
The transfer block needs to be removed by the current provider/Registrar. The domain transfer can then be restarted via the Hetzner Robot.
This error message usually occurs with .de/.at domains only. An example of such an error message:
--- status: failed transaction: QRO20100831152413-021702400-812318t2 message: - text: Required glue record is missing. argument: ns1.your-server.de. level: error code: 318 - text: Required glue record is missing. argument: ns2.your-server.de. level: error code: 318 reference: 812318
If the hostnames of the nameservers are located within the new domain, then glue records need to be entered into the
Primary Nameserver und
Secondary Nameserver input fields:
In the example below, the relevant nameservers
<18.104.22.168> for the domain
<yourserver.de> should be
1. Nameserver and
2. Nameserver must be filled out in the Robot as follows (Hostname + space + IP address):
ns1.yourserver.de 22.214.171.124 ns2.yourserver.de 126.96.36.199
Should the glue record also yield an IPv6 address as well as an IPv4 address, the entries must read as follows:
ns1.yourserver.de 188.8.131.52 12ab:23cd:34ef:0:0:0:0:1 ns2.yourserver.de 184.108.40.206 12ab:23cd:34ea:0:0:0:0:1
For .com/.net/.org/.info/.biz/.eu domains, the registration of nameservers is necessary via the Robot instead of specifying the IP address.
This error message usually occurs with .de domains only. An example of such an error message:
--- status: failed transactionID: QRO20100831152413-021702400-812318t2 message: - text: Nameserver error. argument: 'ERROR: 902 Timeout (target) (ns1.your-server.de/220.127.116.11:53)' level: error code: 319 - text: Nameserver error. argument: 'ERROR: 902 Timeout (target) (ns2.your-server.de/18.104.22.168:53)' level: error code: 319 reference: 812318
Creating the corresponding DNS entry for the domain on the nameservers specified for the domain has probably been forgotten here.
Should Robot nameservers be used for a domain, the DNS entry can be created via the menu item
DNS entries ->
New DNS entry. This should take place before the start of the domain registration/domain transfer.
This error message usually occurs with .de domains. An example of such an error message:
--- status: failed transactionID: QRO20100831152413-021702400-812318t2 message: - text: Nameserver error. argument: 'ERROR: 118 Inconsistent set of NS RRs (IP, NS host names) (ns1.your-server.de/22.214.171.124, [ns1.your-server.de, ns3.your-server.de])' level: error code: 319 - text: Nameserver error. argument: 'ERROR: 118 Inconsistent set of NS RRs (IP, NS host names) (ns2.your-server.de/126.96.36.199, [ns1.your-server.de, ns3.your-server.de])' level: error code: 319 reference: 812318
This message means that the nameserver entries (NS records) in the DNS entry for the corresponding domain do not match the nameservers specified for the domain. Either the zone file or the entries need to be adjusted in the Robot.
In the example above, the nameservers
<ns2.your-server.de> are specified for the domain. However, only the NS records for
<ns3.your-server.de> have been placed in the DNS entry.
Nameserver not found in database and/or
Host YourNameserver.de not found on domain registration/-transfer/-update
If your own nameservers are to be specified for .com/.net/.org/.info/.biz/.eu domains these must first be registered via the domain registration Robot (Menu item
DNS entries ->
Registered nameservers). Subsequently, the domain update /transfer/registration can be attempted once more.