Hey all,
When setting up a remote SQL server that I'd like to manage within cpanel, it would be excellent if the "skip name resolve" feature could be used. This is useful and standard practice. One, there is a performance benefit (no matter how minute you may think it is) to this option when you skip the name resolution. Two, I may have multiple cpanel servers with a user that I want to tie in to the same database on the same SQL server. This is especially useful when I'm attempting to 'decouple' a user's application so I can distribute it across a fleet of servers. It is a supreme pain right now to make this work if a client wants cpanel on their admin side of their setup. I tend to recommend they skip cPanel entirely right now due to this limitation for larger clients. Sort of related, a method of allowing the creation of users via "%" instead of the hostname. It doesn't even have to be a configuration in whm, I'd settle for an includes file or something that I can put directives in.
I was merged into this, not sure if we're both shooting for the same thing. That I know of, what I'd like to do has never worked. For a recap:
I may have multiple cPanel servers with a user that I want to tie in to the same database on the same SQL server. This is especially useful when I'm attempting to 'decouple' a user's application so I can distribute it across a fleet of servers. It is a supreme pain right now to make this work if a client wants cPanel on their admin side of their setup. I tend to recommend they skip cPanel entirely right now due to this limitation for larger clients. Sort of related, a method of allowing the creation of users via "%" instead of the hostname. It doesn't even have to be a configuration in WHM, I'd settle for an includes file or something that I can put directives in.
I was merged into this, not sure if we're both shooting for the same thing. That I know of, what I'd like to do has never worked. For a recap:
I may have multiple cPanel servers with a user that I want to tie in to the same database on the same SQL server. This is especially useful when I'm attempting to 'decouple' a user's application so I can distribute it across a fleet of servers. It is a supreme pain right now to make this work if a client wants cPanel on their admin side of their setup. I tend to recommend they skip cPanel entirely right now due to this limitation for larger clients. Sort of related, a method of allowing the creation of users via "%" instead of the hostname. It doesn't even have to be a configuration in WHM, I'd settle for an includes file or something that I can put directives in.
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
Most MySQL tuning scripts recommend disabling name resolution which makes a lot of sense. Why can't we use this with cPanel??
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
Most MySQL tuning scripts recommend disabling name resolution which makes a lot of sense. Why can't we use this with cPanel??
I'm going to bring this up to our developers to see if we can nail down why this isn't supported currently in the product, or if there's something else we can do to help these situations. It may be a week or two before I'm able to get a solid answer, due to vacations around the holidays, but I'll be back as soon as I have more information.
I'm going to bring this up to our developers to see if we can nail down why this isn't supported currently in the product, or if there's something else we can do to help these situations. It may be a week or two before I'm able to get a solid answer, due to vacations around the holidays, but I'll be back as soon as I have more information.
Hi,
FYI Steps to reproduce:
Enable skip-name-resolve in config.Add a user via cPanel > Mysql UsersAssign user to database and try to give all privileges
Error: There was a problem adding the user: (XID j8zau2) Database Error: Can't find any matching row in the user table
Before version 60 this gave a warning but everything still worked. Better solution would be to support this completely. It shouldn't be to hard to simply avoid setting hostnames if skip-name-resolve is in use.
Hi,
FYI Steps to reproduce:
Enable skip-name-resolve in config.Add a user via cPanel > Mysql UsersAssign user to database and try to give all privileges
Error: There was a problem adding the user: (XID j8zau2) Database Error: Can't find any matching row in the user table
Before version 60 this gave a warning but everything still worked. Better solution would be to support this completely. It shouldn't be to hard to simply avoid setting hostnames if skip-name-resolve is in use.
It will be a very good option for everyone if skip-name-resolve not conflict with user permission in database and in back up in cpanel. Please add this function to work with cpanel.
It will be a very good option for everyone if skip-name-resolve not conflict with user permission in database and in back up in cpanel. Please add this function to work with cpanel.
+1. We don't need no DNS resolution.
+1. We don't need no DNS resolution.
+1, DNS resolutions make everything slow, specially when you have the MySQL port 3306 open to the world (which is not a very good idea, but it's sometimes needed to do so due to dynamic IPs)
While it is possible to add the skip-name-resolve option nowadays without breaking the MySQL server for those using localhost as their mysql_host; the mysql error log get's filled with warnings from each hostname that's already added to the permissions table, so it's annoying to say the least.
+1, DNS resolutions make everything slow, specially when you have the MySQL port 3306 open to the world (which is not a very good idea, but it's sometimes needed to do so due to dynamic IPs)
While it is possible to add the skip-name-resolve option nowadays without breaking the MySQL server for those using localhost as their mysql_host; the mysql error log get's filled with warnings from each hostname that's already added to the permissions table, so it's annoying to say the least.
Hey all! Just a quick update to let you know: this is being tracked internally as CPANEL-20491. It hasn't been picked up by any teams yet, but if/when it does I'll be back to let everyone know.
Hey all! Just a quick update to let you know: this is being tracked internally as CPANEL-20491. It hasn't been picked up by any teams yet, but if/when it does I'll be back to let everyone know.
I would like to see this supported! Seems inefficient to make DNS queries for database calls.
I would like to see this supported! Seems inefficient to make DNS queries for database calls.
Certainly something that should be supported. It is a common option that is used on databases configured to run only on localhost and deny connections from remotes. Shared servers would stand to gain the most convenience from this option being supported.
Certainly something that should be supported. It is a common option that is used on databases configured to run only on localhost and deny connections from remotes. Shared servers would stand to gain the most convenience from this option being supported.
I would also like to be able to set this variable to true. This variable also affects full account restores. Without it, restores are broken.
I would also like to be able to set this variable to true. This variable also affects full account restores. Without it, restores are broken.
Hi Benny,
Any progress towards CPANEL-20491 ?
Thanks.
Hi Benny,
Any progress towards CPANEL-20491 ?
Thanks.
Too often I encounter "feature unsupported" for very typical server configuration options, like this one. We pay for cpanel to make server management easier, not more difficult by searching for weird workarounds instead of using standard mysql features.
Too often I encounter "feature unsupported" for very typical server configuration options, like this one. We pay for cpanel to make server management easier, not more difficult by searching for weird workarounds instead of using standard mysql features.
Replies have been locked on this page!