trace on CoreDNS: DNS and Service Discoveryhttps://coredns.website.cncfstack.com/tags/trace/Recent content in trace on CoreDNS: DNS and Service DiscoveryHugo -- gohugo.ioen-usCoreDNS - All Rights ReservedMon, 13 Jul 2026 15:51:55 +0000tracehttps://coredns.website.cncfstack.com/plugins/trace/Mon, 13 Jul 2026 15:51:55 +0000https://coredns.website.cncfstack.com/plugins/trace/Description With trace you enable OpenTracing of how a request flows through CoreDNS. Enable the debug plugin to get logs from the trace plugin. Syntax The simplest form is just: trace [ENDPOINT-TYPE] [ENDPOINT] ENDPOINT-TYPE is the type of tracing destination. Currently only zipkin and datadog are supported. Defaults to zipkin. ENDPOINT is the tracing destination, and defaults to localhost:9411. For Zipkin, if ENDPOINT does not begin with http, then it will be transformed to http://ENDPOINT/api/v2/spans.