Files
coredns/middleware/whoami
Miek Gieben 2cff9291e5 mw/whoami: update docs (#1054)
* mw/whoami: update docs

Parse the corefile in the readme_test.go and other tweaks to the docs.

Fixes #1049

* trailing

* remove the 53 port
2017-09-10 20:46:25 +01:00
..
2017-09-10 20:46:25 +01:00
2016-09-17 17:09:05 +01:00

whoami

whoami returns your resolver's local IP address, port and transport. Your IP address is returned in the additional section as either an A or AAAA record.

The reply always has an empty answer section. The port and transport are included in the additional section as a SRV record, transport can be "tcp" or "udp".

._<transport>.qname. 0 IN SRV 0 0 <port> .

If CoreDNS can't find a Corefile on startup this is the default middleware that gets loaded. As such it can be used to check that CoreDNS is responding to queries. Other than that this middleware is of limited use in production.

The whoami middleware will respond to every A or AAAA query, regardless of the query name.

Syntax

whoami

Examples

Start a server on the default port and load the whoami middleware.

. {
    whoami
}

When queried for "example.org A", CoreDNS will respond with:

;; QUESTION SECTION:
;example.org.   IN       A

;; ADDITIONAL SECTION:
example.org.            0       IN      A       10.240.0.1
_udp.example.org.       0       IN      SRV     0 0 40212