Skip to content

Conversation

ishanjain28
Copy link

Summary

This PR fixes #904

It updates the endpoint code to resolve a domain with the specified custom resolver if specified or go to the default resolver as fallback

No documentation changes are required since this fixes a bug

Checklist

  • Tested and/or added tests to validate that the changes work as intended, if applicable.
  • Updated documentation in README.md, if applicable.

@github-actions github-actions bot added the bug Something isn't working label Apr 18, 2025
@ishanjain28 ishanjain28 force-pushed the use_custom_resolver branch from 5ced376 to 5087627 Compare May 3, 2025 21:47
@ishanjain28
Copy link
Author

@TwiN I addressed the PR feedback and it is ready for review again.

@ishanjain28
Copy link
Author

Hi @TwiN, This PR is ready to be reviewed. Please let me know if you have any queries

Comment on lines +63 to +65
// DNSResolverConfig is parsed DNSResolver
// We do this to avoid parsing DNSResolver every time it is needed
DNSResolverConfig *DNSResolverConfig `yaml:"-"`
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this isn't a configuration, it shouldn't be exported and thus it should be dnsResolver.
Also, move it next to httpClient (if you have the time, please move both (httpClient and dnsResolver at the bottom of the struct)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect IP when using dns-resolver

2 participants