coredns/man/coredns-nsid.7

.\" Generated by Mmark Markdown Processer - mmark.miek.nl
.TH "COREDNS-NSID" 7 "August 2020" "CoreDNS" "CoreDNS Plugins"

.SH "NAME"
.PP
\fInsid\fP - adds an identifier of this server to each reply.

.SH "DESCRIPTION"
.PP
This plugin implements RFC 5001
\[la]https://tools.ietf.org/html/rfc5001\[ra] and adds an EDNS0 OPT
resource record to replies that uniquely identify the server. This is useful in anycast setups to
see which server was responsible for generating the reply and for debugging.

.PP
This plugin can only be used once per Server Block.

.SH "SYNTAX"
.PP
.RS

.nf
nsid [DATA]

.fi
.RE

.PP
\fBDATA\fP is the string to use in the nsid record.

.PP
If \fBDATA\fP is not given, the host's name is used.

.SH "EXAMPLES"
.PP
Enable nsid:

.PP
.RS

.nf
example.org {
    whoami
    nsid Use The Force
}

.fi
.RE

.PP
And now a client with NSID support will see an OPT record with the NSID option:

.PP
.RS

.nf
% dig +nsid @localhost a whoami.example.org

;; Got answer:
;; \->>HEADER<<\- opcode: QUERY, status: NOERROR, id: 46880
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 3

\&....

; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; NSID: 55 73 65 20 54 68 65 20 46 6f 72 63 65 ("Use The Force")
;; QUESTION SECTION:
;whoami.example.org.        IN    A

.fi
.RE

.SH "ALSO SEE"
.PP
RFC 5001
\[la]https://tools.ietf.org/html/rfc5001\[ra]