MySQL could not be resolved: Temporary failure in name resolution報(bào)錯的解決方法

本篇內(nèi)容介紹了“MySQL could not be resolved: Temporary failure in name resolution報(bào)錯的解決方法”的有關(guān)知識，在實(shí)際案例的操作過程中，不少人都會遇到這樣的困境，接下來就讓小編帶領(lǐng)大家學(xué)習(xí)一下如何處理這些情況吧！希望大家仔細(xì)閱讀，能夠?qū)W有所成！

最近幾天研發(fā)總是抱怨用Navicat連接MySQL數(shù)據(jù)庫和打開數(shù)據(jù)表很慢，登錄數(shù)據(jù)庫分析，查看錯誤日志：


mysql> show variables like 'log_error';
+---------------+--------------------------------+
| Variable_name | Value                          |
+---------------+--------------------------------+
| log_error     | /usr/local/mysql/data/idb3.err |
+---------------+--------------------------------+
1 row in set (0.00 sec)


查看錯誤日志:

[root@idb3 data]# cat /usr/local/mysql/data/idb3.err | grep failure |more
2016-05-24 16:06:44 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:06:47 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:00 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:03 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:14 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
..........................................................................................................................

解決方法:
在mysql的配置文件my.cnf中
[mysqld]
節(jié)點(diǎn)添加下面兩行

skip-host-cache
skip-name-resolve         

參數(shù)解釋如下:
skip-host-cache:禁用主機(jī)名緩存
skip-name-resolve:禁用主機(jī)名解析        

然后重啟MySQL數(shù)據(jù)庫即可解決:
# service mysqld restart

“MySQL could not be resolved: Temporary failure in name resolution報(bào)錯的解決方法”的內(nèi)容就介紹到這里了，感謝大家的閱讀。如果想了解更多行業(yè)相關(guān)的知識可以關(guān)注億速云網(wǎng)站，小編將為大家輸出更多高質(zhì)量的實(shí)用文章！