coredns/plugin/nsid
Miek Gieben b003d06003
For caddy v1 in our org (#4018)
* For caddy v1 in our org

This RP changes all imports for caddyserver/caddy to coredns/caddy. This
is the v1 code of caddy.

For the coredns/caddy repo the following changes have been made:

* anything not needed by us is deleted
* all `telemetry` stuff is deleted
* all its import paths are also changed to point to coredns/caddy
* the v1 branch has been moved to the master branch
* a v1.1.0 tag has been added to signal the latest release

Signed-off-by: Miek Gieben <miek@miek.nl>

* Fix imports

Signed-off-by: Miek Gieben <miek@miek.nl>

* Group coredns/caddy with out plugins

Signed-off-by: Miek Gieben <miek@miek.nl>

* remove this file

Signed-off-by: Miek Gieben <miek@miek.nl>

* Relax import ordering

github.com/coredns is now also a coredns dep, this makes
github.com/coredns/caddy fit more natural in the list.

Signed-off-by: Miek Gieben <miek@miek.nl>

* Fix final import

Signed-off-by: Miek Gieben <miek@miek.nl>
2020-09-24 18:14:41 +02:00
..
log_test.go Clean up tests logging (#1979) 2018-07-19 16:23:06 +01:00
nsid.go Fix NSID not being set on cached responses (#3822) 2020-04-27 08:49:56 -07:00
nsid_test.go complete nsid plugin test case (#3981) 2020-07-01 10:17:26 +02:00
README.md update doc to not use the root zone for everything (#3288) 2019-09-19 06:17:53 -07:00
setup.go For caddy v1 in our org (#4018) 2020-09-24 18:14:41 +02:00
setup_test.go For caddy v1 in our org (#4018) 2020-09-24 18:14:41 +02:00

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