Solution skill
Diag: agent DNS failure on intake, test from the agent network namespace
Complete solution
Shows how to fix diag: agent DNS failure on intake, test from the agent network namespace. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Restart the agent after network changes. Add the intake endpoints to your network runbook so the next firewall change does not repeat this.
Steps
- Symptom (exact): forwarder errors mentioning DNS failure / no such host for the intake endpoint of your site. Everything else on the box resolves fine.
- Likely causes: (a) egress DNS blocked for the agent (VPC resolver rules, firewall), (b) proxy configured without DNS handling, (c) wrong site hostname typo in config, (d) split-horizon DNS in the VPC.
- From the agent host (and from inside the agent container netns if containerized), resolve the intake hostname for your site. Fails here, works from your laptop: it is the host/VPC DNS path.
- Check
datadog.yamlfor a hand-typed endpoint override with a typo. The default per-site endpoints need no override; customdd_urlvalues are a smell. - If behind a proxy: does the proxy do the DNS, or does the agent? Misconfigured proxy DNS is the classic corporate case.
- Compare against a known-good host in the same subnet. Same failure means subnet/VPC-level, not the box.
- Fix: allow DNS egress to the resolver, fix the proxy DNS settings, remove the typoed override, or add the VPC resolver rule. Restart the agent after network changes.
- Verify: resolution succeeds from the agent netns, forwarder accepts payloads, host appears in Infrastructure. Add the intake endpoints to your network runbook so the next firewall change does not repeat this.
When to use
You are seeing this: Symptom (exact): forwarder errors mentioning DNS failure / no such host for the intake endpoint of your site. Use this skill when you run into "Diag: agent DNS failure on intake, test from the agent network namespace".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
The site docs list the per-region intake endpoints the agent must reach; the agent proxy docs cover DNS-through-proxy behavior. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_oIhlny4zeVK1qfY7yQEh_g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diag: agent DNS failure on intake, test from the agent network namespace <span>— Vectle</span></a>