Add script to check connectivity after set up nameservers #849
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
This was referenced Apr 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Below are some of the changes I made:
Study Case:
There are special cases where changing the nameservers to 1.1.1.1 or 8.8.8.8 results in loss of connectivity.
ISPs usually do DNS blocking, so unallowed DNS (3rd party DNS) can't work. I also experienced a similar failure case when installing on several servers in Indonesia.
When the nameservers are changed to 1.1.1.1 and 8.8.8.8, the installer stops at SWAP Set..
The code that I added functions to check when the nameserver is finished changing and will return the nameserver settings to default when a connectivity failure occurs.