mbatch hang/bsub hang issue caused by slowly resolution

We have experienced the following issues. For more information, please refer to case number TS005350597.
If any DNS issue happens, egroup resolution is very slow and mbatchd waits for egroup.
egroup resolution slow -> mbatchd wait for egroup -> bsub hang -> sbatchd monitor mbatchd and found mbatchd had no response -> sbatchd kill mbatchd and restart mbatchd -> egroup resolution done -> LSF recover and bsub works

And here's the additional content.
---------------------------------------------------------------------------
Let me summarize the test result:

1. Add sleep into egroup script to simulate slow egroup.
2. mbatchd stop working and wait for egroup response. bsub also hang.
3. badmin reconfig and badmin mbdrestart are also slow because they also resolve egroup.
4. sbatchd does not get a response from mbatchd for a long time. Then sbatchd kills mbatchd and restart mbatchd.
5. mbatchd restart and resolve egroup.

If then egroup resolution is quick, LSF works.
If egroup resolution is still slow, LSF hang.

Above result is design behavior, not a defect.
---------------------------------------------------------------------------

After discussing the above,
Our customer requested one function.

If any DNS issue happens, egroup resolution is very slow and mbatchd waits for egroup.
After that, bsub hang occurs.

The customer requested that the issue of mbatchd hang/bsub hang does not occur even if DNS issues occur.

We would like to ask you if we can release features to avoid these issues in the future.

In addition, it would be highly appreciated if you could consider whether LSF 11 can avoid such an issue.