E
EricF
The morning started with a too early morning call - my application's reverse
DNS lookups were all failing. There was a network "hiccup" the night before.
We ended up restarting the server and everything was fine.
It turns out that Java by default caches all failed DNS lookups with no
expiration. I think this is a very bad idea.
I came across this blog while researching the issue ...
http://www.burnthacker.com/articles/search?q=dns
Eric
DNS lookups were all failing. There was a network "hiccup" the night before.
We ended up restarting the server and everything was fine.
It turns out that Java by default caches all failed DNS lookups with no
expiration. I think this is a very bad idea.
I came across this blog while researching the issue ...
http://www.burnthacker.com/articles/search?q=dns
Eric