Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve the problem of IP address could not be resolved error reporting in mysql database". The content in the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to solve the problem of IP address could not be resolved error reporting in mysql database".

I just got in touch with the mysql database, so I don't know a lot of things. Today, when I looked at the newly built mysql, I found that there were a lot of warning in the log. I checked it myself, and people on the Internet said

This warning will not affect database access, but when a large number of such logs are generated, the previous error messages in the database will be difficult to query. The greater the number of connections, the higher the frequency of alarm logs.

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 12:59:16 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

2014-08-13 13:00:36 3149 [Warning] IP address' 172.17.206.195' could not be resolved: Temporary failure in name resolution

The cause of the problem:

The reason for the error is that MYSQL Server maintains a non-local Client TCP cache in local memory, which contains the login information of the remote Client, such as IP address, hostname, and so on.

If Client connects to the server, Mysql will first resolve the client's hostname or anti-resolution based on the IP address in the local TCP pool. If it cannot be resolved, it will resolve it in DNS. If the resolution still fails, such a warning message will be written in error log.

The solution:

1. You can disable this function with two parameters, and add the following parameters to [mysqld] in the configuration file of MYSQL:

[mysqld]

Skip-host-cache

Skip-name-resolv

It prevents MySql Server from doing DNS parsing of external connections, and using this option eliminates the time that MySql parses DNS. However, this will cause a problem: when connecting to mysql

Can not use localhost to connect, but to use IP (127.0.0.1) address; if you press localhost to assign permissions to users, the user login permissions should also be modified

Thank you for reading, the above is the content of "how to solve the problem of IP address could not be resolved error in mysql database". After the study of this article, I believe you have a deeper understanding of how to solve the problem of IP address could not be resolved error in mysql database, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.