IP addresses, ports, ids, and query types are given in hexadecimal format.
tinydns logs this entry immediately before entering its receive/process/respond loop while telling on which IP it is bound.
tinydns attempted to respond to a request. The attempt may have failed due to a network error, but such errors are not logged.
Field Meaning
ip The IP address from which the request was received,
and to which the response was sent.
port The port number from which the request was received,
and to which the response was sent.
id The request id, which the client picks
and the server includes in the response.
type The type of records requested.
name The domain name for which records were requested.
tinydns
dropped a request because it did not have the authority to answer.
It only has the authority to answer if it has an SOA record for name or a suffix of name.
Note that if it is unable to open the data.cdb file, it will have no authority for any domain.
The fields have the same meanings as in the + log entry.
tinydns received a request that it does not implement, or that had invalid bits set in the header, so it responded with an rcode of 4 (NOTIMP). For example, if the client asks tinydns to perform a recursive query, or any type of query except a standard query, then tinydns creates this type of log entry and responds with a NOTIMP answer. The fields have the same meanings as in the + log entry.
tinydns received a query for a class other than IN (Internet) or 255, so it responded with an rcode of 1 (FORMERR). Class 255 means "any class". The fields have the same meanings as in the + log entry. Note that the actual class in the query is not logged, so there is no reliable way to decode the meaning of the type field.
tinydns received a request packet that either contained no query, contained more than one query, or otherwise could not be parsed. tinydns dropped the request. The ip and port fields have the same meanings as in the + log entry. The other field values are hardcoded.
Reversely, dropped requests are given as