When testing their name servers, after querying the EPP server, accredited registrars receive a response in the form of a detailed line that is both human- and machine-readable.

In machine output mode, these responses are transmitted in the form of result codes that can all be interpreted by a person based on the corresponding definition.

These codes are also interpreted in a human-visible detailed line. The text resulting from this interpretation includes $$0$$ as replacement characters for arguments in the position indicated by the number between the dollar signs. Make sure that the first argument starts at 0!

Champ ‘id’ Definition Field ‘text…’ 
MSG_CACHE_NOADDRHOST (1)

A name server with a given IP address does not exist in the nameserver-test cache.

 Missing host '$$0$$' with address '$$1$$' from cache
MSG_CACHE_NOHOST (2)

A given name server does not exist in the test name server cache.

 Missing host '$$0$$' from cache
MSG_CFG_BAD_VALUE (3)

The new value of a given configuration option was not understood.

 Invalid configuration value for $$0$$
MSG_CFG_NO_SUCH_OPTION (4)

The given configuration option is unknown.

 Unknown configuration option $$0$$
MSG_CFG_UPDATED (5)

The given configuration option has been modified.

 Configuration option $$0$$ updated
MSG_EMPTY_ANSWER (6)

A name server responded with a blank reply; that name server does not know the tested domain name.

 Answer for $$0$$ query from $$1$$ at address $$2$$ contains no answer
MSG_GLUENS_NO_IPADDRESS (7)

A local name server that requires a glue record did not provide an IP address and cannot be resolved/used.

 Missing address for local nameserver $$0$$
MSG_MULTI_SOA_ANSWER (8)

A given name server provided multiple SOA records in its response.

 Nameserver '$$0$$' at address '$$1$$' returned too many SOA records ($$2$$)
MSG_MULTIPLE_MASTER (9)

For the tested domain name, multiple masters have been announced by the name servers.

 Multiple master servers exist for the domain name '$$0$$'.
MSG_NO_ANSWER (10)

A name server did not respond to any of the DNS queries sent to it.

 No answer from $$0$$ at address $$1$$
MSG_NO_ANSWER_FOR_QUERY (11)

A name server did not respond to a given DNS query.

 No answer for $$0$$ query from $$1$$ at address $$2$$
MSG_NO_AUTH_NAMESERVER (12)

The name server test did not return any authoritative name server.

 No working authoritative nameserver found
MSG_NON_AUTH_ANSWER (13)

A name server responded with a non-authoritative answer to a given query. This name server is probably a simple resolver.

 Answer for $$0$$ query from $$1$$ at address $$2$$ is not authoritative
MSG_NS_ADV_NO_GLUE (14)

A given name server is not displaying its own IP address as a ‘glue record’.

 Nameserver '$$0$$' at address '$$1$$' does not provide its address as glue record
MSG_NS_NO_ADV_SELF (15)

A given name server is not listing itself as the authoritative server for the tested domain.

 Nameserver '$$0$$' at address '$$1$$' does not advertise itself as nameserver
MSG_NS_ZONE_MASTER (16)

List of name servers that advertise for a given zone master.

 Master '$$0$$' is advertised by nameservers at addresses: $$1$$
MSG_NSTEST_DOMAIN (17)

Indicates the domain name for which the test is being performed.

 Nameserver test for domain $$0$$
MSG_NSTEST_HOST_DISCOVERED (18)

Indicates a discovered name server. (name server not listed in the test request)

 Nameserver $$0$$ at $$1$$ (discovered)
MSG_NSTEST_HOST_PROVIDED (19)

Indicates a name server provided in the request. (name server indicated in the request)

 Nameserver $$0$$ at $$1$$ (provided)
MSG_QUERY_FAILED (20)

A name server responded with a failure code for a given query.

 $$0$$ query failed for nameserver '$$1$$' at address '$$2$$' ($$3$$)
MSG_REQ_BAD_COMMAND (21)

Command unknown.

 Unknown command '$$0$$'
MSG_REQ_BAD_HOSTNAME (22)

Host name not valid/not well-formed.

 Invalid host name '$$0$$'  
MSG_REQ_BAD_IPADDRESS  (23)

IP address not valid/not well-formed for a given name server.

 Failed to decode IP address '$$1$$' for host '$$0$$'    
MSG_REQ_PARSE_FAILED (24)

Command not valid/not well-formed, the command could not be parsed.

 Request parsing error    
MSG_REQ_TOO_FEW_ARGS (25)

Arguments missing for the command. More arguments are expected.

 Too few arguments
MSG_RESOLVE_FAILED (26)

Cannot resolve the given non-glue name server.

 Failed to resolve external nameserver '$$0$$
MSG_RESOLVE_NOMATCH  (27)

The name server resolved to a different IP address than the IP address provided/previously detected.

 External nameserver '$$0$$' does not resolve to provided address '$$1$$'
MSG_SINGLE_AUTH_NAMESERVER (28)

Only one authoritative name server was detected.

 Only one working authoritative nameserver found  
MSG_SYS_SESSION_END  (29)

The server ends the session. (after the quit command)

 Closing connection  
MSG_SYS_USAGE  (30)

Usage information line.

 $$0$$  
MSG_TOO_FEW_AUTH_NAMESERVER (31)  

Not enough authoritative name servers were found; indicate the minimum number expected.

 At least $$0$$ nameservers required  
MSG_TRUNCATED_ANSWER_FOR_QUERY (32)

The response to a DNS query was truncated because it doesn't fit into the UDP response packet. The DNS client must therefore re-send the query using the TCP protocol.

 Answer for $$0$$ query from $$1$$ at address $$2$$ is truncated  
MSG_INTERNAL_ERROR (33)

Internal error

 Internal error  
MSG_UDP_EMPTY_ANSWER (34) 

A name server responded with a blank reply using UDP. That name server does not know the tested domain name.

 [UDP] Answer for $$0$$ query from $$1$$ at address $$2$$ contains no answer
MSG_TCP_EMPTY_ANSWER (35)

A name server responded with a blank reply using TCP. That name server does not know the tested domain name.

 [TCP] Answer for $$0$$ query from $$1$$ at address $$2$$ contains no answer.  
MSG_UDP_NS_ADV_NO_GLUE (36)

A given name server did not show its own IP address as a glue record when queried by UDP.

 [UDP] Nameserver '$$0$$' at address '$$1$$' does not provide its address as glue record  
MSG_TCP_NS_ADV_NO_GLUE (37)

A given name server did not provide its own IP address as a glue record when queried via TCP.

 [TCP] Nameserver '$$0$$' at address '$$1$$' does not provide its address as glue record.  
MSG_UDP_NS_NO_ADV_SELF (38)

A given name server is not listing itself as an authoritative server for the tested domain when queried by UDP.

 [UDP] Nameserver '$$0$$' at address '$$1$$' does not advertise itself as nameserver   
MSG_TCP_NS_NO_ADV_SELF (39)

A given name server is not announcing itself as an authoritative server for the tested domain when queried by TCP.

 [TCP] Nameserver '$$0$$' at address '$$1$$' does not advertise itself as nameserver
MSG_UDP_MULTI_SOA_ANSWER (40)

A given name server provided multiple SOA records in its response when queried by UDP.

[UDP] Nameserver '$$0$$' at address '$$1$$' returned too many SOA records ($$2$$)  
MSG_TCP_MULTI_SOA_ANSWER  (41)

A given name server provided multiple SOA records in its response when queried by TCP.

 [UDP] Nameserver '$$0$$' at address '$$1$$' returned too many SOA records ($$2$$)  
MSG_UDP_RESOLVE_NOMATCH (42)

The name server resolved to a different IP address than the IP address provided/previously detected.

 [UDP] External nameserver '$$0$$' does not resolve to provided address '$$1$$'  
MSG_TCP_RESOLVE_NOMATCH (43)

The name server resolved to a different IP address than the IP address obtained/previously detected.

 [TCP] External nameserver '$$0$$' does not resolve to provided address '$$1$$'  
MSG_UDP_NO_ANSWER_FOR_QUERY (44)

A name server did not respond to a given DNS query via UDP.

  [UDP] No answer for $$0$$ query from $$1$$ at address $$2$$.  
MSG_TCP_NO_ANSWER_FOR_QUERY  (45)

A name server did not respond to a given DNS query via TCP.

  [TCP] No answer for $$0$$ query from $$1$$ at address $$2$$$.  
MSG_UDP_NO_ANSWER  (46)

A name server did not respond to any of the DNS queries sent to it by UDP.

 [UDP] No answer from $$0$$ at address $$1$$  

MSG_TCP_NO_ANSWER (47)

A name server did not respond to any of the DNS queries sent to it by TCP.

 [TCP] No answer from $$0$$ at address $$1$$  
MSG_UDP_QUERY_FAILED  (48)

A name server responded with a failure code for a given query using UDP.

 [UDP] $$0$$ query failed for nameserver '$$1$$' at address '$$2$$' ($$3$$)
MSG_TCP_QUERY_FAILED (49)

A name server responded with a failure code for a given query using TCP.

 [TCP] $$0$$ query failed for nameserver '$$1$$' at address '$$2$$' ($$3$$)  
MSG_UDP_NON_AUTH_ANSWER  (50)

A name server responded with an non-authoritative answer to a given query using UDP. This name server is probably a simple resolver.

 [UDP] Answer for $$0$$ query from $$1$$ at address $$2$$ is not authoritative  
MSG_TCP_NON_AUTH_ANSWER (51)

A name server responded with an non-authoritative answer to a given query using TCP. This name server is probably a simple resolver.

 [TCP] Answer for $$0$$ query from $$1$$ at address $$2$$ is not authoritative
MSG_FAILED  (52)

A name server responded with a failure code for a given query.

 Query failed for nameserver '$$0$$' at address '$$1$$' ($$2$$)  
MSG_UDP_FAILED  (53)

A name server responded with a failure code for a given query.

 [UDP] Query failed for nameserver '$$0$$' at address '$$1$$' ($$2$$)  
MSG_TCP_FAILED  (54)

A name server responded with a failure code for a given query.

 [TCP] Query failed for nameserver '$$0$$' at address '$$1$$' ($$2$$)
MSG_ANSWER_DIFFERING_FOR_QUERY (55)  

The responses to the same query from UDP and TCP are different.

 Answer for $$0$$ query from $$1$$ at address $$2$$ differs between UDP and TCP transports  
MSG_TRUNCATED_ANSWER_FOR_QUERY_NO_TCP  (56)  

The response to a DNS query was truncated because it doesn't fit into the UDP response packet. The attempt to resend the request using TCP failed.

 Answer for $$0$$ query from $$1$$ at address $$2$$ is truncated but TCP query impossible  
MSG_TCP_TRUNCATED_ANSWER_FOR_QUERY (57)

The response to a DNS query sent by TCP is truncated. It makes no sense.

 TCP answer for $$0$$ query from $$1$$ at address $$2$$ is unexpectedly truncated   
MSG_REQ_BAD_DS_RECORD (58)

The indicated DS record is malformed. It must contain the keytag, the algorithm, the digest type, and the digest's HEX code.

 Invalid DS record '$$0$$'  
MSG_DNSSEC_OK  (59)

The DNSSECs were successfully validated.

 [DNSSEC] Validation successful using NS '$$0$$' at address '$$1$$': $$2$$

MSG_DNSSEC_NO_KEY (60)

No DNSKEY record available.

 [DNSSEC] No DNSKEY record found using NS '$$0$$' at address '$$1$$' : $$2$$$
MSG_DNSSEC_KEY_2_DS_FAILED (61)

An error occurred when attempting to convert available DNSKEY records into DS records.

 [DNSSEC] Failed to convert DNSKEY to DS using NS '$$0$$' at address '$$1$$': $$2$$  
MSG_DNSSEC_DS_NO_MATCH (62)

The listed DS records do not match the available DNSKEYs.

 [DNSSEC] No DS - DNSKEY match found using NS '$$0$$' at address '$$1$$': $$2$$  
MSG_DNSSEC_VALIDATION_FAILED (63)

DNSSEC validation failed, check the key hardware, the key/signature expiry dates, and the consistency of the zone! The validation error may give a hint as to what isn't working.

 [DNSSEC] Validation failed using NS '$$0$$' at address '$$1$$': $$2$$  
MSG_DNSSEC_TIMEOUT (64)

DNSSEC validation took too much time, check that the DNS servers are not overloaded!

 [DNSSEC] Timeout while validating using NS '$$0$$' at address '$$1$$  
MSG_DNSSEC_CACHE_NOADDRHOST (65)

No DNSSEC validation is available in the cache for the given list of DS records.

 [DNSSEC] Missing host '$$0$$' with address '$$1$$' from cache