Background (please complete the following information):
Describe the bug
/var/www/pterodactyl To Reproduce
Steps to reproduce the behavior:
DatabasesYou can only use IP'sSee screenshot:

Expected behavior
I expect that hostnames should work and that pterodactyl could verify a connection instead of blindly rejecting everything not being an IP.
The connection works when I spin up a tool called _adminer_ and assign it to the same network, and connect by hostname.
I run my mysql database in docker, which I have attached to the pterodactyl_nw-network. Pterodactyl does not operate with static subnets, so a host restart may cause the ranges to change. In such cases, I also need to change the IP in the panel for the database, since it operates on the same range. If it operated by hostname, it would have kept the connection without any action from my side. Unsure why this is being limited..
So why not use the ip then? That's not even a valid fqdn, That's why it's complaining. Mysql.domain.com would be a valid fqdn
In the context of a docker container, it can be a valid FQDN.
Are there any variables among the files that could be changed to override this value whilst this is being tracked here?