Update zeroconf to show that the interface configuration has been centralized in the network integration (#17911)

* Update zeroconf.markdown

* Update zeroconf.markdown
This commit is contained in:
J. Nick Koston 2021-06-02 05:55:43 -05:00 committed by GitHub
parent fc29c12ecb
commit 278c93f9fe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -29,11 +29,6 @@ zeroconf:
description:
type: map
keys:
default_interface:
description: By default, `zeroconf` will attempt to detect the best value based on available routing information. For systems that require broadcasting mDNS on all interfaces, change this option to `false` if `zeroconf` does not function.
required: false
type: boolean
default: true
ipv6:
description: By default, `zeroconf` will enable IPv6 support. If your network has trouble with IPv6 being enabled, you can set this option to `false`.
required: false
@ -41,10 +36,6 @@ zeroconf:
default: true
{% endconfiguration %}
## `default_interface` auto detection
## Network interfaces and auto detection
If the `default_interface` is unset, the value is auto-detected based on the system routing next hop for the mDNS broadcast address (`224.0.0.251`).
If the next-hop cannot be detected or is a loopback address, `zeroconf` will broadcast on all interfaces. If the next hop is a non-loopback address, `zeroconf` will only broadcast on the default interface.
Setting the `default_interface` to `true` or `false` will override the auto detection.
Zeroconf chooses which interfaces to broadcast on based on the [Network](/integrations/network/) integration.