This has been a long week, with MySQL fails left right and centre.

The actual MySQL server ships with a bomb ready to go off as we found out at work. For every connection to the server it does DNS lookups for the user to verify where the connection is coming from and for a production server all connections will be from a limited amount of known hosts. So when the hosting provider’s DNS blows up in your face, you are left with a MySQL server which is not allowing any connections what so ever, the web servers go nuts with requests failing and retrying and a lot of clients on the phone giving you a good ear bashing. (Plus the boss gets a headache)

You can switch the DNS lookups off, the solution was found here:

http://www.mysqlperformanceblog.com/2008/05/31/dns-achilles-heel-mysql-installation/

Another fail comes in the form of the Administrator GUI tool which started today. When connecting to a remote database through an SSH tunnel, (which might I add has worked for the past 2 years.) I get the wonderful 2013 MySQL error, sadly Google has yet to provide me with a solution, however Navicat Lite has provided a clue which is the also unhelpful: Lost connection to MySQL Server at ‘reading initial communication packet’, system error: 0.

If I find a solution, I’ll post it here.

Ah well, at least the weekend is now here, I can go get drunk off my face and make a tit of myself in front of the general public. Also I’ve just realised that Grey Area is now 2 years old! A rather quiet celebration as there is no user base here.