coredns/man/coredns-debug.7

.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-DEBUG" 7 "March 2021" "CoreDNS" "CoreDNS Plugins"

.SH "NAME"
.PP
\fIdebug\fP - disables the automatic recovery upon a crash so that you'll get a nice stack trace.

.SH "DESCRIPTION"
.PP
Normally CoreDNS will recover from panics; using \fIdebug\fP inhibits this. The main use of \fIdebug\fP is
to help in testing. A side effect of using \fIdebug\fP is that \fB\fClog.Debug\fR and \fB\fClog.Debugf\fR messages
will be printed to standard output.

.PP
Note that the \fIerrors\fP plugin (if loaded) will also set a \fB\fCrecover\fR, negating this setting.

.PP
Enabling this plugin is process-wide: enabling \fIdebug\fP in at least one server block enables
debug mode globally.

.SH "SYNTAX"
.PP
.RS

.nf
debug

.fi
.RE

.PP
Some plugins will send debug log DNS messages. This is done in the following format:

.PP
.RS

.nf
debug: 000000 00 0a 01 00 00 01 00 00 00 00 00 01 07 65 78 61
debug: 000010 6d 70 6c 65 05 6c 6f 63 61 6c 00 00 01 00 01 00
debug: 000020 00 29 10 00 00 00 80 00 00 00
debug: 00002a

.fi
.RE

.PP
Using \fB\fCtext2pcap\fR (part of Wireshark), this can be converted back to binary, with the following
command line: \fB\fCtext2pcap -i 17 -u 53,53\fR, where 17 is the protocol (UDP) and 53 are the ports. These
ports allow Wireshark to detect these packets as DNS messages.

.PP
Each plugin can decide whether to dump messages to aid in debugging.

.SH "EXAMPLES"
.PP
Disable the ability to recover from crashes and show debug logging:

.PP
.RS

.nf
\&. {
    debug
}

.fi
.RE

.SH "SEE ALSO"
.PP
https://www.wireshark.org/docs/man-pages/text2pcap.html
\[la]https://www.wireshark.org/docs/man-pages/text2pcap.html\[ra].