🤖 Add DNS Validation and Resolution Logic#363
Merged
doubleangels merged 1 commit intodevfrom Jan 21, 2025
Merged
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
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.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by DoubleAngels
Fixes NEXTDNS-MANAGER-1AT
This pull request introduces a new utility class, DNSResolver, which provides methods to validate NextDNS subdomains and resolve hostnames with retry logic. In VisualIndicator.java, logic has been added to validate the hostname of requests to ensure they are valid NextDNS subdomains. If the hostname is invalid, a message is sent to Sentry. Additionally, the code now attempts to resolve the hostname of requests, capturing errors if resolution fails, and handling specific network exceptions to improve resilience and error reporting.
If you have any questions or feedback for the Sentry team about this fix, please email autofix@sentry.io with the Run ID: 3404.