Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm testing our backups and I'm running into problems with the mysql accounts. I can't log in from one (restored) server to another (restored) mysql server. The logs show me that it's denying the user 'apache_auth'@, whereas on the priviliges table the user is in as 'apache_auth' However if I ping from the mysql server, i can see that it's getting the IP address of How come it's not doing the reverse?

share|improve this question

Check your MySQL config file (like /etc/my.cnf) and see if your db server has skip-name-resolve enabled. More info:

Also, tail the error log (specified and enabled by log-error) or the warning log (log-warnings). More info: I don't remember which one of them would have logs on denied access.

share|improve this answer
up vote 0 down vote accepted

This was my own fault. we're using an internal 192.168.0.x network, with our own nameserver to resolve 'db1' to 192.168.0.x. However I haven't set up the reverse ARPA / PTR entries. Which obviously means it's not resolveing IP addresses.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.