ethernal
January 28th, 2008, 02:57 AM
Due to upstreams DNS issue, u20.eset.com got resolved to completely wrong IP adress.
I recorded my internal ESS clients lodging about 5-10 HTTP GET requests per second, per client.
Basically, it got resolved to a website that doesnt offer 404's, but rather shows their graphic heavy start page instead.
So when ESS wanted to auto-update to u20.eset.com and the update.ver it didnt know what to do with it, and consequently kept hammering.
On average, each client generated about 30-40mb of traffic every ten minutes due to this <_<
Please, would you consider having some sort of sanity check on the auto-update procedure. if you don't get the expected reply, please don't immediatly try again. thank you
I recorded my internal ESS clients lodging about 5-10 HTTP GET requests per second, per client.
Basically, it got resolved to a website that doesnt offer 404's, but rather shows their graphic heavy start page instead.
So when ESS wanted to auto-update to u20.eset.com and the update.ver it didnt know what to do with it, and consequently kept hammering.
On average, each client generated about 30-40mb of traffic every ten minutes due to this <_<
Please, would you consider having some sort of sanity check on the auto-update procedure. if you don't get the expected reply, please don't immediatly try again. thank you