> Have a look here:
> You may want to start mysqld with the --skip-name-resolve option.
Thanks for the reply. I did see that page before, but
I guess my bigger question is why if the DNS is broken/slow, why
does the entire server come to a COMPLETE halt, no commands can
be done via either TCP *OR* the socket. If it just errored, that
session took forever, whatever... I could understand. The problem
is that when it gets probed, it COMPLETELY offlines (DOS) the server.
And just *1* connection!
Just also seems difficult to keep proper documentation if
we are using IPs and not complete hostnames.
> Tuc at T-B-O-H <ml@stripped> wrote:
> > Hi,
> > We seem to be running into a problem with our
> > installation that we don't understand.
> > We are running "mysql-server-4.0.25" from
> > the ports collection on a FreeBSD 5.3-RELEASE-p10
> > machine. Its tcpwrapper'd to only allow from our
> > /24, and a single machine outside the /24.
> > At times, all of a sudden the server seems
> > to "freeze". It appears that we've narrowed it down
> > to an issue with people attacking the server that
> > come from a site that has a bad reverse DNS setup.
> > Has anyone else seen this, or knows how
> > to stop it?
> > Thanks, Tuc
> For technical support contracts, goto https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.NET http://www.ensita.net/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Gleb Paharenko
> / /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
> /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
> <___/ www.mysql.com
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1