Fix DNS router reset when network changed#4078
Closed
everyx wants to merge 1 commit into
Closed
Conversation
nekohasekai
force-pushed
the
stable
branch
5 times, most recently
from
8631cb2 to
2b995ea
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
DNS resolution times out after system resume on Linux because
NetworkManager.ResetNetwork()fails to reset the DNS router.This leaves DNS transport connection pools (UDP/DoH) in a stale state while other components are correctly reset. Calling
DNSRouter.ResetNetwork()withinNetworkManagerensures that DNS cache and connections are refreshed upon any network state change.