MY-010058 'xxx' does not resolve warnings while bound to 127.0.0.1 only

I have some of these warnings in mysql/error.log every day:

2024-05-24T21:55:50.340286Z 0 [Warning] [MY-010058] [Server] Hostname ‘visit.keznews.com’ does not resolve to ‘194.165.16.37’.
2024-05-25T16:32:46.014896Z 0 [Warning] [MY-010055] [Server] IP address ‘45.227.254.55’ could not be resolved: Name or service not known
2024-05-25T16:48:12.827107Z 0 [Warning] [MY-010055] [Server] IP address ‘207.90.244.14’ could not be resolved: Name or service not known
2024-05-25T19:24:39.554134Z 0 [Warning] [MY-010055] [Server] IP address ‘45.227.254.8’ could not be resolved: Name or service not known

Why does mysqld try to resolve those names and addresses?
MySQL runs on the local / loop device only:

[mysqld]
bind-address    = 127.0.0.1,::1

So no access from “outside” should be possible…

I just found the answer myself:

~# netstat -plnt | grep mysql
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 4038/mysqld
tcp6 0 0 :::33060 :::* LISTEN 4038/mysqld
tcp6 0 0 ::1:3306 :::* LISTEN 4038/mysql

It’s the “new” X-protocoll.

I also have to add

mysqlx-bind-address = 127.0.0.1,::1

Silly me.