docs: add firewall and redirect trouble shooting commands #9
Conversation
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.
PR description:
Added two short troubleshooting sections to README.md: "Port Check - Firewall" and "Port Check - Traffic Redirect". These show concrete dnstt-client commands to test direct server connectivity on the service port (5300) and on port 53 before redirection. I spent about 4 hours diagnosing an issue where my cloud provider blocked UDP port 53, and these notes should help others detect the same problem faster.
Notes:
This change is purely documentation.
Open to any edits or suggestions.