Skip to content

fix(relay): Disable DNS caching#4213

Open
aldy505 wants to merge 1 commit intomasterfrom
aldy505/fix/relay-disable-dns-cache
Open

fix(relay): Disable DNS caching#4213
aldy505 wants to merge 1 commit intomasterfrom
aldy505/fix/relay-disable-dns-cache

Conversation

@aldy505
Copy link
Collaborator

@aldy505 aldy505 commented Mar 13, 2026

@github-actions
Copy link

Changelog Preview

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

  • Reorder pull images by aldy505 in #4202

Bug Fixes 🐛

  • (relay) Disable DNS caching by aldy505 in #4213
  • Manual image tags rollback to nightly by aldy505 in #4204

Internal Changes 🔧

Deps

  • Bump actions/setup-node from 6.2.0 to 6.3.0 by dependabot in #4206
  • Bump getsentry/craft from 2.21.7 to 2.23.2 by dependabot in #4207
  • Bump minimatch from 9.0.5 to 9.0.7 in /_integration-test/nodejs by dependabot in #4189

🤖 This preview updates automatically when you update the PR.

# better performance, it's recommended to keep it enabled if possible.
#
# The default value is `true`.
dns_cache: false
Copy link

Choose a reason for hiding this comment

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

Bug: The dns_cache: false setting in config.example.yml is not commented out, which will disable DNS caching by default for all new installations, degrading performance.
Severity: MEDIUM

Suggested Fix

Comment out the dns_cache: false line and its parent http key in relay/config.example.yml. This will make it an optional setting that users can enable if needed, consistent with other workarounds in the file.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: relay/config.example.yml#L34

Potential issue: The `config.example.yml` file, used for new installations, now includes
`dns_cache: false` as an active, uncommented setting. This contradicts the file's own
comments, which describe it as a workaround for specific DNS issues and state the
default is `true`. Other workarounds in the file are commented out by default. By
leaving this setting active, all new self-hosted installations will experience
performance degradation from disabled DNS caching, even if they do not have the
underlying DNS problem this setting is intended to solve.

Did we get this right? 👍 / 👎 to inform future reviews.

Copy link
Collaborator

@aminvakil aminvakil left a comment

Choose a reason for hiding this comment

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

I do not think this is a good default to disable all dns queries caching.

More: getsentry/sentry#109002 (comment)

Copy link
Collaborator

@aminvakil aminvakil left a comment

Choose a reason for hiding this comment

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

Honestly I'm still on both sides about merging this as it is, or with dns_cache: true by default.

@aldy505
Copy link
Collaborator Author

aldy505 commented Mar 13, 2026

Honestly I'm still on both sides about merging this as it is, or with dns_cache: true by default.

@aminvakil yeah lets hold this off for a while

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

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Relay HealthCheck failed

2 participants