This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
Configurable resolver timeout #1524
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OTRS uses hardcoded 3s timeout for DNS queries while checking MX (if CheckMXRecord is enabled). 3s may be too short in some scenarios (sporadic errors in MX validation of remote addresses). DNS timeout should be configurable to allow admin to fine-tune this setting. This mod introduces new SysConfig parameter ResolverTimeout that allows one to set custom timeout for DNS queries fired by OTRS (now only for CheckMXRecord algo). Related: https://dev.ib.pl/ib/otrs/issues/99 Author-Change-Id: IB#1058919
|
Hello Pawel, this has been in OTRS for a very long time, and so far I was not aware of problems with that. I think that such an issue is rather a problem with the IT infrastructure and should be solved at this level. |
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OTRS uses hardcoded 3s timeout for DNS queries while checking MX
(if CheckMXRecord is enabled). 3s may be too short in some scenarios
(sporadic errors in MX validation of remote addresses). DNS timeout
should be configurable to allow admin to fine-tune this setting.
This mod introduces new SysConfig parameter ResolverTimeout that
allows one to set custom timeout for DNS queries fired by OTRS
(now only for CheckMXRecord algo).
Related: https://dev.ib.pl/ib/otrs/issues/99
Author-Change-Id: IB#1058919