Remote connection Mysql Database note logging (remote connection slow skip-name-resolve) _mysql

First, how to create a new independent account and set permissions

Here I use Navicat as my database management tool to open the navicat.

Select "User"--"New user"

Enter user name, host, password, it should be noted that the host is not write "localhost", but write "%"

You can then set the server permissions

and specify the permissions for the database, and then save the exit

Second, remote connection slow

Slow is a big problem, the online approach is to My.ini "[mysqld]" Add a line under "skip-name-resolve", like this:

Then save and restart the MySQL service.

The following are additional users:

The problem is this:

I started a MySQL on a machine (61.183.23.23) and opened an account that could be accessed from 127.0.0.1 or 61.183.23.23. But a problem is when you use the following two command line access, the speed difference is very large:

Mysql–h 127.0.0.1–u User
Mysql–h 61.183.23.23–u User

Then I use ping to determine the speed of two IP is similar.

Using 127.0.0.1 IP is much faster than the other. Although it is said that the 61.183.23.23 need to go outside the net to walk a lap, but how the speed difference is so much worse.

Solution:

MySQL uses skip-name-resolve to disable DNS queries.
MySQL will be in the user login process to the client IP DNS back-check, whether you are using IP login or domain name login, the process is in the reverse investigation. So if your MySQL server has a problem with DNS or bad quality, then it is possible to cause this problem I encountered, DNS resolution problems.

Modify MySQL configuration file

[Mysqld]
Skip-name-resolve

Add:

To make a reminder, increase skip-name-resolve may cause account invalidation, such as my original account is yejianfeng@localhost, then actually I use Mysql-h127.0.0.1-uyejianfeng can log in. But once you add a skip-name-resolve, you can't log in. Need to add account yejianfeng@127.0.0.1

Database plus this parameter speed will be faster skip-name-resolve, but also have the attention point, Mysql.user table inside the host do not use localhost and so on, to use 127.0.0.1 or even their own database, will complain

I'm not going to add skip-name-resolve now, Now create a root user but the domain is 127.0.0.1, and then the Skip-name-resolve Plus, you can use root login, new users directly with 127.0.0.1, so OK.