Regarding DNS cache in Jelastic

Some of our customers have experienced issues when they try to contact external services.

The issue is caused by nscd that cache DNS requests.
Because of a bug in glibc the TTL for a record isn't honored.

The good news is that we've located the issue and that it's isolated to a specific
version of glibc. Jelastic have provided a fix and patched all the containers. In order for
the fix to work the environment need to be stopped and then started.

Please note that it's not sufficient to only restart the container service.

If you experience issues with external services not responding, we kindly ask you to restart your environment once. You're welcome to contact the support via the usual channels, in case you need help with this.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Article is closed for comments.