I have an Ubuntu server with MySQL 5.5 installed. In /var/lib/mysql a .err file is kept on updating with these warnings only:

[Warning] IP address '' could not be resolved: Temporary failure in name resolution
[Warning] IP address '' could not be resolved: Temporary failure in name resolution

Its size is currently around 2 GB.

I googled this error and in most of the places it has been written that I need to write skip-host-cache in my.cnf file and then need to give a restart mysql.

Currently this server is carrying lot of running web services, applications and giving a restart may effect all these applications.

As far as I understand, these warnings are not native mysql errors.

Also, can someone tell me whether these warnings effect my database in future if I will not take any action and is it possible that due to other web applications, these errors are generating? What is the other way around for this without restarting mysql?

IS there any probability , that mysql will not come up after restart ???

2 Answers 2


Put the following parameters in your my.cnf and then restart the service:-


The above activity will solve your issue.

Try to check this link also:-


  • bit - is restarting mysql only option we have ? what if mysql will not come up ??? im afraid it will impact my ongoing applications May 6, 2014 at 11:56
  • skip-name-resolve is not a dynamic variable, hence you will have to put this parameter in your cnf file and then restart required. you can change log-warning parameter value dynamically, for this no restart required.
    – abhinavbit
    May 6, 2014 at 12:02
  • i have set log_warnings = 0 , but it is not resolving my issue May 6, 2014 at 12:28
  • you will have to put skip-name-resolve in your cnf to resolve the issue.
    – abhinavbit
    May 6, 2014 at 12:29
  • yes , i had already put same..in mysqld section May 6, 2014 at 12:39

When connecting to Mysql remotely, I got the error. I had this warning in /var/log/mysqld.log:

[Warning] IP address 'X.X.X.X' could not be resolved: Temporary failure in name resolution

I just added this line to /etc/hosts file:

X.X.X.X some_name

Problem solved! without using skip-name-resolve, it caused some errors in my local app, when connecting to mysql.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.