npm · npm:@opentelemetry/instrumentation-dns
@opentelemetry/instrumentation-dns active
OpenTelemetry instrumentation for `node:dns` name resolution module
The latest stable version of @opentelemetry/instrumentation-dns is 0.68.0, published on 2026-11-05. Verified by Vigia on 2026-11-13.
| Latest stable version | 0.68.0 |
|---|---|
| Published | 2026-11-05 21:38:36 UTC |
| Install | npm install @opentelemetry/instrumentation-dns@latest |
| Requires (engines) | {"node":">=22.15.0"} |
| Peer dependencies | @opentelemetry/api ^1.10.0 |
| Dist-tags | latest: 0.68.0 |
| License | Apache-2.0 |
| Advisories on latest version | none known |
| Last verified | 2026-11-13 01:50:59 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Ask your AI assistant to check this
AI models are trained up to a date, so they can be wrong about versions, deprecations and vulnerabilities. Paste this into Claude, ChatGPT, Perplexity or Cursor and it will answer with the verified data on this page:
Before answering about the npm package "@opentelemetry/instrumentation-dns", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-dns . For my whole project use https://vigia.coredls.cloud/context
Using an AI coding agent every day? Connect Vigia once and it checks this by itself.
Maintenance
| Activity | active |
|---|---|
| Last stable release | 2026-10-20 21:16:22 UTC · 23 days ago |
| Stable releases in the last 12 months | 15 |
| Published versions | 68 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
0.67.0 | 2026-10-20 21:16:22 UTC |
0.66.0 | 2026-10-06 15:23:55 UTC |
0.65.0 | 2026-08-31 20:39:15 UTC |
0.64.0 | 2026-07-23 17:57:19 UTC |
0.63.0 | 2026-07-03 08:32:06 UTC |
0.62.0 | 2026-06-11 14:54:37 UTC |
0.61.0 | 2026-05-13 10:30:59 UTC |
0.60.0 | 2026-05-06 14:30:40 UTC |
0.59.0 | 2026-04-29 19:29:43 UTC |
0.58.0 | 2026-04-17 14:41:32 UTC |
0.57.0 | 2026-03-26 00:24:17 UTC |
0.56.0 | 2026-03-04 17:11:19 UTC |
0.55.0 | 2026-02-17 07:37:32 UTC |
0.54.0 | 2026-01-22 10:01:43 UTC |
0.53.0 | 2026-01-15 10:24:37 UTC |
0.52.0 | 2025-11-06 18:00:57 UTC |
0.51.0 | 2025-10-21 16:00:53 UTC |
0.50.0 | 2025-10-06 19:10:19 UTC |
0.49.2 | 2025-09-29 19:41:00 UTC |
0.49.1 | 2025-09-29 18:24:11 UTC |
Showing the 20 most recent of 68 versions. JSON
Version compatibility
Newest stable version that declares support for each runtime version (from the requirements published with each version).
| Runtime | Newest compatible version |
|---|---|
node 16 | 0.43.1 |
node 18 | 0.66.0 |
node 20 | 0.66.0 |
node 22 | 0.67.0 |
node 24 | 0.67.0 |
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What is the latest version of @opentelemetry/instrumentation-dns?
The latest stable version of @opentelemetry/instrumentation-dns is 0.68.0, published on 2026-11-05. Verified by Vigia on 2026-11-13.
How do I install the latest version of @opentelemetry/instrumentation-dns?
Run npm install @opentelemetry/instrumentation-dns@latest. The latest stable version is 0.68.0 (verified 2026-11-13).
Is @opentelemetry/instrumentation-dns deprecated?
No. @opentelemetry/instrumentation-dns is not marked as deprecated in the registry.
Which Node.js version does @opentelemetry/instrumentation-dns require?
@opentelemetry/instrumentation-dns 0.68.0 declares this requirement: {"node":">=22.15.0"}.
Does @opentelemetry/instrumentation-dns 0.68.0 have known vulnerabilities?
No known advisories affect @opentelemetry/instrumentation-dns 0.68.0 according to the data Vigia checks.
Is @opentelemetry/instrumentation-dns still maintained?
@opentelemetry/instrumentation-dns published 15 stable releases in the last 12 months; the most recent was 23 days ago. Activity: active.
Observed changes
- Fri Nov 06 2026 01:48:19 GM +0000 (Coordinated Universal Time) — released 0.68.0 → 0.68.0
- hu Nov 05 2026 21:48:17 GMT+0000 (Coordinated Universal Time) — released 0.67.0 → 0.68.0
- ue Oct 20 2026 23:03:38 GMT+0000 (Coordinated Universal Time) — runtime_requirement_changed
- ue Oct 20 2026 23:03:38 GMT+0000 (Coordinated Universal Time) — released 0.66.0 → 0.67.0
- Wed Oct 07 2026 11:42:18 GM +0000 (Coordinated Universal Time) — released 0.66.0 → 0.66.0
- ue Oct 06 2026 15:40:04 GMT+0000 (Coordinated Universal Time) — released 0.65.0 → 0.66.0
Related packages
- @opentelemetry/api
- static-eval
- @hapi/bourne
- promise-polyfill
- @graphql-codegen/add
- @storybook/addon-highlight
- relay-runtime
- babel-plugin-react-compiler
- react-test-renderer
- @oxlint/binding-linux-x64-gnu
- stoppable
- murmurhash-js
- @azure-rest/core-client
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-dns) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-dns) [](https://vigia.coredls.cloud/npm/@opentelemetry/instrumentation-dns)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-dns
GET https://vigia.coredls.cloud/v1/packages/npm/@opentelemetry/instrumentation-dns/versions/{version}