History

Miek Gieben 004c5fca9d all: simply registering plugins (#3287 ) Abstract the caddy call and make it simpler. See #3261 for some part of the discussion. Go from: ~~~ go func init() { caddy.RegisterPlugin("any", caddy.Plugin{ ServerType: "dns", Action: setup, }) } ~~~ To: ~~~ go func init() { plugin.Register("any", setup) } ~~~ This requires some external documents in coredns.io to be updated as well; the old way still works, so it's backwards compatible. Signed-off-by: Miek Gieben <miek@miek.nl>		2019-09-20 08:02:30 +01:00
..
log_test.go	Clean up tests logging (#1979 )	2018-07-19 16:23:06 +01:00
nsid.go	all: fix plugin import ordering (#1717 )	2018-04-22 08:34:35 +01:00
nsid_test.go	all: fix plugin import ordering (#1717 )	2018-04-22 08:34:35 +01:00
OWNERS	Add OWNERS file (#1486 )	2018-02-08 10:55:51 +00:00
README.md	update doc to not use the root zone for everything (#3288 )	2019-09-19 06:17:53 -07:00
setup.go	all: simply registering plugins (#3287 )	2019-09-20 08:02:30 +01:00
setup_test.go	Update Caddy to 1.0.1, and update import path (#2961 )	2019-07-03 09:04:47 +08:00

README.md

nsid

Name

nsid - adds an identifier of this server to each reply.

Description

This plugin implements RFC 5001 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.

This plugin can only be used once per Server Block.

Syntax

nsid [DATA]

DATA is the string to use in the nsid record.

If DATA is not given, the host's name is used.

Examples

Enable nsid:

example.org {
    whoami
    nsid Use The Force
}

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

% 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

Also See

RFC 5001