Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to use Miekg by default #4519

Merged
merged 3 commits into from Aug 5, 2021
Merged

Conversation

clyang82
Copy link
Contributor

@clyang82 clyang82 commented Aug 4, 2021

Signed-off-by: clyang82 chuyang@redhat.com

  • I added CHANGELOG entry for this change.
  • Change is not relevant to the end user.

Changes

ref: #4204
I saw the same issue exists in version 0.22 in OCP 4.8.
If I understand correctly, Miekg resolver was working fine for everyone, but Go native not. so have this PR to use Miekg as default resolver.

Verification

Signed-off-by: clyang82 <chuyang@redhat.com>
Signed-off-by: clyang82 <chuyang@redhat.com>
@clyang82
Copy link
Contributor Author

clyang82 commented Aug 4, 2021

/retest

GiedriusS
GiedriusS previously approved these changes Aug 4, 2021
Copy link
Member

@GiedriusS GiedriusS left a comment

Choose a reason for hiding this comment

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

I have personally encountered problems with the Go DNS resolver as well - it was resolving some of the records but not all of them. Switching to miekgdns had helped me. So, I agree with this PR 👍

CHANGELOG.md Outdated
@@ -19,6 +19,7 @@ We use *breaking :warning:* to mark changes that are not backward compatible (re

- [#4468](https://github.com/thanos-io/thanos/pull/4468) Rule: Fix temporary rule filename composition issue.
- [#4476](https://github.com/thanos-io/thanos/pull/4476) UI: fix incorrect html escape sequence used for '>' symbol.
- [#4519](https://github.com/thanos-io/thanos/pull/4519) Store: fix cannot unmarshal DNS message errors.
Copy link
Member

Choose a reason for hiding this comment

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

I would probably write Query: switch to miekgdns DNS resolver as the default one under the Changed section instead 😄

Signed-off-by: clyang82 <chuyang@redhat.com>
@clyang82
Copy link
Contributor Author

clyang82 commented Aug 4, 2021

/retest

Copy link
Contributor

@yeya24 yeya24 left a comment

Choose a reason for hiding this comment

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

LGTM

@GiedriusS GiedriusS merged commit 0e9cc46 into thanos-io:main Aug 5, 2021
@clyang82 clyang82 deleted the dns-resolver branch August 5, 2021 08:25
squat pushed a commit that referenced this pull request Dec 23, 2022
Related to issue: #4204

Problem: in the PR #4519 the
default sd-dns-resolver for querier was set to miekgdns but this change
was never ported to ruler

Solution: this PR brings this default to ruler as well to make it
consistent

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>
ngraham20 pushed a commit to ngraham20/thanos that referenced this pull request Apr 17, 2023
Related to issue: thanos-io#4204

Problem: in the PR thanos-io#4519 the
default sd-dns-resolver for querier was set to miekgdns but this change
was never ported to ruler

Solution: this PR brings this default to ruler as well to make it
consistent

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>
ngraham20 pushed a commit to ngraham20/thanos that referenced this pull request Apr 17, 2023
Related to issue: thanos-io#4204

Problem: in the PR thanos-io#4519 the
default sd-dns-resolver for querier was set to miekgdns but this change
was never ported to ruler

Solution: this PR brings this default to ruler as well to make it
consistent

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>

Signed-off-by: JoaoBraveCoding <jmarcal@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants