Description of problem: I'm using replication and the MySQL servers are occasionally caching the wrong values for hostnames (see URL). It appears that all the users who reported the bug to MySQL are Red Hat users. Version-Release number of selected component (if applicable): mysql-server-4.1.14-1.FC4.1 How reproducible: sometimes Steps to Reproduce: 1.Set up replication 2.access master from many hosts (sorry this is vague) 3.watch for inconsistencies: make a connection from foo.example.com and do SELECT USER(); Actual results: notice that it says user.com Expected results: user.com Additional info: Problem goes away when we disable the MySQL host cache. $ grep hosts /etc/nsswitch.conf hosts: dns nis [NOTFOUND=return] files Nothing freaky in /etc/hosts $ ypcat hosts 127.0.0.1 localhost loghost 129.234.4.13 timehost 129.234.4.78 nsrhost 127.0.0.1 localhost loghost The DNS entries don't change (!) getent hosts foo.example.com and its IP works fine. Running NSCD but I've had this problem with NSCD turned off too. ObSecurity: I assert that this is a possible security problem because many sites use host-based MySQL access control rules. It certainly caused me a denial of service when the replication master had the wrong value for the replication slave.
You should file this with www.mysql.com; it's unlikely that I'd be able to find the problem. Nor do I see any reason to think it's a Red Hat rather than MySQL bug.
I'm sorry, I was sure I'd filled in the URL field that showed the MySQL bug (http://bugs.mysql.com/bug.php?id=13659). The reason I've filed it with Red Hat as well is: * each of the reporters has been running a Red Hat distribution of some form * MySQL AB don't think it's their bug (though they haven't told us why yet, admittedly). <sigh> I guess I'll go and chase MySQL a bit more...
Ah, I missed the link to an upstream bug report. I see that the latest comment there acknowledges that it probably is a MySQL bug. I'm going to close this entry as being filed upstream; but feel free to reopen this report if it does turn out to be Red Hat specific, or if MySQL provide a fix in a future update.