MySQL has skip_name_resolve disabled and attempts reverse DNS lookups that time out or fail. The DNS server is unreachable or misconfigured on the MySQL host. The connecting IP has no PTR record in DNS

Step 1: Disable reverse DNS lookups in my.cnf: add `skip_name_resolve` under `[mysqld]` and restart MySQL.. Step 2: If skip_name_resolve is enabled, ensure all GRANT statements use IP addresses, not hostnames.. Step 3: Alternatively, add a PTR record for the client IP in your DNS configuration.

Medium severityconnection

Power BI Refresh Error:
1042

What does this error mean?

MySQL cannot perform a reverse DNS lookup for the connecting client's IP address.

Common causes

1MySQL has skip_name_resolve disabled and attempts reverse DNS lookups that time out or fail
2The DNS server is unreachable or misconfigured on the MySQL host
3The connecting IP has no PTR record in DNS

How to fix it

1Step 1: Disable reverse DNS lookups in my.cnf: add `skip_name_resolve` under `[mysqld]` and restart MySQL.
2Step 2: If skip_name_resolve is enabled, ensure all GRANT statements use IP addresses, not hostnames.
3Step 3: Alternatively, add a PTR record for the client IP in your DNS configuration.

Frequently asked questions

What does skip_name_resolve do in MySQL?

It disables reverse DNS lookups for incoming connections. MySQL uses IP addresses only for access control, which is faster and more reliable in cloud environments.

Do I need to change existing GRANTs after enabling skip_name_resolve?

Yes — existing grants using hostnames (e.g., 'user'@'myserver.example.com') will no longer match. Convert them to IP-based grants or use wildcards ('user'@'%').

Can MetricSign detect intermittent failures caused by DNS issues?

Yes — MetricSign tracks ADF pipeline failure patterns over time, making intermittent DNS-related failures visible as recurring incidents.

Official documentation: https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html