Domain Robot Error FAQ

Last change on 2023-01-30 • Created on 2023-01-30 • ID: RO-840C3

Introduction

This article provides answers to common error messages for the Domain Registration Robot.

I have already created handles but cannot select these when configuring a domain

Handles are always tied to the respective domain ending (TLD). For example, only .de handles can be used for .de domains.

I cannot use the handle I created for all the roles

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

Error message Illegal operation on own domain. when starting a domain transfer

Here is 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 you can't start a domain transfer. Instead, you need a Hetzner internal domain transfer for the domain.

Error message Object status prohibits operation. on starting a domain transfer

This error message usually occurs with .com/.net/.org/.info/.biz domains. Here's 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 something similar). You can check on this by doing a whois query, for example.

The current provider/registrar needs to remove the transfer block. Then you can restart the domain transfer via the Hetzner Registration Robot.

Error message Required glue record is missing. on domain registration/-transfer/-update

This error message usually only occurs with .de/.at domains. Here's 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 you need to enter glue records into the Primary Nameserver und Secondary Nameserver input fields:

In the example below, the relevant nameservers <1.1.1.1> and <2.2.2.2> for the domain <yourserver.de> should be <ns1.yourserver.de> and <ns2.yourserver.de>.

You need to fill out the fields 1. Nameserver and 2. Nameserver on Robot as follows (Hostname + space + IP address):

ns1.yourserver.de 1.1.1.1
ns2.yourserver.de 2.2.2.2

Should the glue record also yield an IPv6 address as well as an IPv4 address, the entries must read as follows:

ns1.yourserver.de 1.1.1.1 12ab:23cd:34ef:0:0:0:0:1
ns2.yourserver.de 2.2.2.2 12ab:23cd:34ea:0:0:0:0:1

For .com/.net/.org/.info/.biz/.eu domains, you need to register the nameservers via Robot instead of specifying the IP address.

Error message DNS-Timeout on domain registration/-transfer/-update

This error message usually only occurs with .de domains. Here's 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/1.1.1.1:53)'
    level: error
    code: 319
  -
    text: Nameserver error.
    argument: 'ERROR: 902 Timeout (target) (ns2.your-server.de/2.2.2.2:53)'
    level: error
    code: 319
reference: 812318

Here, you probably forgot to create the corresponding DNS entry for the domain on the nameservers specified for the domain.

If you want to use Robot nameservers a domain, you can create the DNS entry via the menu item DNS entries -> New DNS entry. You should do this before starting the domain registration/domain transfer.

Error message Inconsistent set of NS RRs on domain registration/-transfer/-update

This error message usually occurs with .de domains. Here's 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/1.1.1.1, [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/2.2.2.2, [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. You either need to adjust the zone file or the entries on Robot.

In the example above, the nameservers <ns1.your-server.de> and <ns2.your-server.de> are specified for the domain. However, only the NS records for <ns1.your-server.de> and <ns3.your-server.de> have been placed in the DNS entry.

Error message Nameserver not found in database and/or Host YourNameserver.de not found on domain registration/-transfer/-update

If you want to specify your own nameservers for .com/.net/.org/.info/.biz/.eu domains, you need to register these first via the Domain Registration Robot (Menu item DNS entries -> Registered nameservers). When you have done that, you can then re-try the domain update /transfer/registration.

Table of Contents