Skip to content
This repository was archived by the owner on Jan 5, 2026. It is now read-only.

Add USE_OS_DNS_RESOLVER env var info#1268

Merged
ejanusevicius merged 4 commits into
mainfrom
agent-os-resolver
Apr 30, 2025
Merged

Add USE_OS_DNS_RESOLVER env var info#1268
ejanusevicius merged 4 commits into
mainfrom
agent-os-resolver

Conversation

@sujaya-sys
Copy link
Copy Markdown
Contributor

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 28, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
checklyhq-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 30, 2025 1:38pm

`HTTP_PROXY`|HTTP proxy configuration for the outbound connection to the Checkly API, used for agent management and monitoring. Used if the proxy server does not accept HTTPS connections. `http://user:password@127.0.0.1:8080`
`JOB_CONCURRENCY`|(Default: 1, max: 10) Number of concurrent checks that are run by the agent.
`LOG_LEVEL`|(Default: `INFO`) Set the log level of the agent. Can be one of `DEBUG`, `LOG`, `INFO`, `WARN` or `ERROR`.
`USE_OS_DNS_RESOLVER`|When set to true, TCP checks will resolve hostnames using the OS’s default DNS settings (`dns.lookup()`), instead of direct DNS queries (`dns.resolve()`). This ensures resolution behaves like it would on the local system (e.g. Kubernetes service names).
Copy link
Copy Markdown
Contributor

@ejanusevicius ejanusevicius Apr 28, 2025

Choose a reason for hiding this comment

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

Considering this is an advanced networking feature, I think we could go a bit lower-level in terms of describing what this env var does.

What do you think about this:

TCP checks will resolve DNS using the underlying getaddrinfo C function of agent OS, instead of using the network. This enables easier DNS resolution for internal services e.g. services running in the same Kubernetes cluster.

ejanusevicius
ejanusevicius previously approved these changes Apr 28, 2025
Copy link
Copy Markdown
Contributor

@ejanusevicius ejanusevicius left a comment

Choose a reason for hiding this comment

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

LGTM!

@ejanusevicius
Copy link
Copy Markdown
Contributor

Merging this as the agent /w this feature has been released.

@ejanusevicius ejanusevicius enabled auto-merge (squash) April 30, 2025 13:36
@ejanusevicius ejanusevicius merged commit f30fea3 into main Apr 30, 2025
5 checks passed
@ejanusevicius ejanusevicius deleted the agent-os-resolver branch April 30, 2025 13:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants