host_cache table provides
access to the contents of the host cache, which contains
client host name and IP address information and is used to
avoid DNS lookups. (See Section 126.96.36.199, “DNS Lookup Optimization and the Host Cache”.) The
host_cache table exposes the
contents of the host cache so that it can be examined using
SELECT statements. The
Performance Schema must be enabled or this table is empty.
TABLE host_cache have the same effect: They clear
the host cache. This also empties the
host_cache table (because it is
the visible representation of the cache) and unblocks any
blocked hosts (see Section B.5.2.6, “Host 'host_name' is blocked”.)
TRUNCATE TABLE requires the
DROP privilege for the
host_cache table has these
The IP address of the client that connected to the server, expressed as a string.
The resolved DNS host name for that client IP, or
NULL if the name is unknown.
Whether the IP-to-host name-to-IP DNS resolution was
performed successfully for the client IP. If
is used as the host name corresponding to the IP so that
calls to DNS can be avoided. While
NO, DNS resolution is attempted again
for each connect, until it eventually completes with
either a valid result or a permanent error. This
information enables the server to avoid caching bad or
missing host names during temporary DNS failures, which
would affect clients forever.
The number of connection errors that are deemed
“blocking” (assessed against the
variable). Currently, only protocol handshake errors are
counted, and only for hosts that passed validation
HOST_VALIDATED = YES).
The number of connections that were blocked because
SUM_CONNECT_ERRORS exceeded the value
The number of transient errors during IP-to-host name DNS resolution.
The number of permanent errors during IP-to-host name DNS resolution.
The number of host name format errors. MySQL does not
perform matching of
Host column values
mysql.user table against host
names for which one or more of the initial components of
the name are entirely numeric, such as
1.2.example.com. The client IP address
is used instead. For the rationale why this type of
matching does not occur, see
Section 6.2.3, “Specifying Account Names”.
The number of transient errors during host name-to-IP reverse DNS resolution.
The number of permanent errors during host name-to-IP reverse DNS resolution.
The number of forward-confirmed reverse DNS errors. These errors occur when IP-to-host name-to-IP DNS resolution produces an IP address that does not match the client originating IP address.
The number of errors that occur because no user from the
client host can possibly log in. In such cases, the server
does not even ask for a user name or password.
The number of errors due to requests for an unavailable authentication plugin. A plugin can be unavailable if, for example, it was never loaded or a load attempt failed.
The number of errors reported by authentication plugins.
An authentication plugin can report different error codes
to indicate the root cause of a failure. Depending on the
type of error, one of these columns is incremented:
COUNT_HANDSHAKE_ERRORS. New return
codes are an optional extension to the existing plugin
API. Unknown or unexpected plugin errors are counted in
The number of errors detected at the wire protocol level.
The number of errors detected when a proxy user A is proxied to another user B who does not exist.
The number of errors detected when a proxy user A is
proxied to another user B who does exist but for whom A
does not have the
The number of errors caused by failed authentication.
The number of errors due to SSL problems.
The number of errors caused by exceeding per-user connection quotas. See Section 6.3.4, “Setting Account Resource Limits”.
The number of errors caused by exceeding per-user connections-per-hour quotas. See Section 6.3.4, “Setting Account Resource Limits”.
The number of errors related to the default database. For example, the database did not exist or the user had no privileges for accessing it.
The number of errors caused by execution failures of
statements in the
The number of errors local to the server implementation and not related to the network, authentication, or authorization. For example, out-of-memory conditions fall into this category.
The number of other, unknown errors not accounted for by
other columns in this table. This column is reserved for
future use, in case new error conditions must be reported,
and if preserving the backward compatibility and table
structure of the
table is required.
The timestamp of the first connection attempt seen from
the client in the
The timestamp of the last connection attempt seen from the
client in the
The timestamp of the first error seen from the client in
The timestamp of the last error seen from the client in
host_cache table was added in