coredns/plugin/bind
Miek Gieben 65458b2de2
Directive -> plugin (#3363)
Caught my eye, we name things directive still, esp when talking about
the prometheus *plugin*. Rename everything that needs to be plugin to
'plugin'. Also make sure Metrics is a H2 section (not H1).

Signed-off-by: Miek Gieben <miek@miek.nl>
2019-10-08 10:20:48 +01:00
..
bind.go plugin register (#3321) 2019-09-28 10:40:43 +01:00
log_test.go Clean up tests logging (#1979) 2018-07-19 16:23:06 +01:00
OWNERS stepdown from CoreDNS maintainer (#2861) 2019-06-03 16:21:05 -04:00
README.md Directive -> plugin (#3363) 2019-10-08 10:20:48 +01:00
setup.go Update Caddy to 1.0.1, and update import path (#2961) 2019-07-03 09:04:47 +08:00
setup_test.go Update Caddy to 1.0.1, and update import path (#2961) 2019-07-03 09:04:47 +08:00

bind

Name

bind - overrides the host to which the server should bind.

Description

Normally, the listener binds to the wildcard host. However, you may want the listener to bind to another IP instead.

If several addresses are provided, a listener will be open on each of the IP provided.

Each address has to be an IP of one of the interfaces of the host.

Syntax

bind ADDRESS  ...

ADDRESS is an IP address to bind to. When several addresses are provided a listener will be opened on each of the addresses.

Examples

To make your socket accessible only to that machine, bind to IP 127.0.0.1 (localhost):

. {
    bind 127.0.0.1
}

To allow processing DNS requests only local host on both IPv4 and IPv6 stacks, use the syntax:

. {
    bind 127.0.0.1 ::1
}

If the configuration comes up with several bind plugins, all addresses are consolidated together: The following sample is equivalent to the preceding:

. {
    bind 127.0.0.1
    bind ::1
}