Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2026-04-13 07:25:37 -04:00
Code Issues Packages Projects Releases Wiki Activity

chore(docs): regenerate man pages (#7971)

Browse Source
This commit is contained in:
Ville Vesilehto
2026-03-27 05:35:09 +02:00
committed by GitHub
parent 49b18b8af6
commit 0132ad86b5
60 changed files with 2110 additions and 280 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
man/coredns-reload.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-RELOAD" 7 "March 2021" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-RELOAD" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -12,7 +12,7 @@ To enable automatic reloading of \fIzone file\fP changes, use the \fB\fCauto\fR
.PP
This plugin periodically checks if the Corefile has changed by reading
it and calculating its MD5 checksum. If the file has changed, it reloads
it and calculating its SHA512 checksum. If the file has changed, it reloads
CoreDNS with the new Corefile. This eliminates the need to send a SIGHUP
or SIGUSR1 after changing the Corefile.
@@ -93,7 +93,7 @@ Check every 10 seconds (jitter is automatically set to 10 / 2 = 5 in this case):
.SH "BUGS"
.PP
The reload happens without data loss (i.e. DNS queries keep flowing), but there is a corner case
where the reload fails, and you loose functionality. Consider the following Corefile:
where the reload fails, and you lose functionality. Consider the following Corefile:
.PP
.RS
@@ -144,7 +144,7 @@ If monitoring is enabled (via the \fIprometheus\fP plugin) then the following me
.PP
Currently the type of \fB\fChash\fR is "md5", the \fB\fCvalue\fR is the returned hash value.
Currently the type of \fB\fChash\fR is "sha512", the \fB\fCvalue\fR is the returned hash value.
.SH "SEE ALSO"
.PP