Am 02.03.2017 um 16:41 schrieb Bruce Ferrell:
There are two ways to approach this:
1.) Turn off name resolution in MySQL and only do the ACL by IP. This is
probably best as name resolution can slow the database and cause
outright app failure if DNS fails for any reason.
2.) Make absolutely certain the names resolve correctly in DNS... Then
see point 1 above.
he is talking about *server* address not the client
that you always should use "skip-name-resolve" and never ever set
permissions based on reverse-DNS because a) when DNS lags everything
lags and b) it is easy for many people which control the PTR of their
zone let it answer what ever yxou wanted to see for grant access
but again: pointing with several hostnames to the same IP has nothing to
do with reverse-lookup at all (nowhere)
on the other hand it makes no sense at all in context of a
database-server because it has no concept of vhosts at all
On 3/2/17 7:01 AM, Kaushal Shriyan wrote:
Is there any pros and cons to multiple domain names mapped to a single IP
work in MySQL client server setup like in case of httpd webserver
there is
a concept of VHost having multiple domain names mapped to a single IP?
For example :-
int-mysqldbserver1.example.com :- 192.168.0.11
int-mysqldbserver2.example.com :- 192.168.0.11
Will there be a issue when i point full qualified domain name in the
application which uses mysql client program since both domain names are
pointing to the same IP?
Any help will be highly appreciable.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
