dog, the command-line DNS client

All possible errors

Because DNS is a relatively simple protocol, it’s possible to list every error that could occur.

Transport errors

Operation timed out

dog did not receive a response to the request it sent within the allowed duration.

Connection refused

dog received a response to the request indicating that the port is closed or inaccessible.

The certificate was not trusted

When using the TLS or HTTPS transport types, the certificate presented by the server was not trusted. This could mean it has expired, it’s for the wrong host, it’s self-signed, or one of the many other reasons this could happen.

Bad Request

The HTTPS nameserver responded with a Bad Request status code.

Record overflow or handshake failure

There was an error in one of the TLS or HTTPS response packets.

Protocol errors

Transaction ID mismatch

We received a response but the first two bytes weren’t correct.

Malformed packet

The DNS data in the response did not conform to the DNS specification.