<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>debug on CoreDNS: DNS and Service Discovery</title><link>https://coredns.website.cncfstack.com/tags/debug/</link><description>Recent content in debug on CoreDNS: DNS and Service Discovery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>CoreDNS - All Rights Reserved</copyright><lastBuildDate>Wed, 28 Oct 2020 18:26:48 +0000</lastBuildDate><atom:link href="https://coredns.website.cncfstack.com/tags/debug/index.xml" rel="self" type="application/rss+xml"/><item><title>debug</title><link>https://coredns.website.cncfstack.com/plugins/debug/</link><pubDate>Wed, 28 Oct 2020 18:26:48 +0000</pubDate><guid>https://coredns.website.cncfstack.com/plugins/debug/</guid><description>Description Normally CoreDNS will recover from panics; using debug inhibits this. The main use of debug is to help in testing. A side effect of using debug is that log.Debug and log.Debugf messages will be printed to standard output.
Note that the errors plugin (if loaded) will also set a recover, negating this setting.
Enabling this plugin is process-wide: enabling debug in at least one server block enables debug mode globally.</description></item></channel></rss>