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 from
Apr 30, 2025
Merged

Add USE_OS_DNS_RESOLVER env var info #1268

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7f31fa1
Add USE_OS_DNS_RESOLVER env var info
sujaya-sys Apr 28, 2025
6ad4bb1
Added feedback by Eddie
sujaya-sys Apr 28, 2025
f04194d
Formatting change
sujaya-sys Apr 28, 2025
118d2cc
Merge branch 'main' into agent-os-resolver
ejanusevicius Apr 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions site/content/docs/private-locations/checkly-agent-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ Variable|Description
`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 •
edited
Loading

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.


For example, you can add these variables to the standard docker run command like this:

Expand Down
Loading