Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: add section to troubleshoot Avahi and mDNS #771

Merged
merged 3 commits into from
Sep 21, 2020
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions TROUBLESHOOTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ Check that:
- on SUSE systems check YaST -> Security and Users -> Firewall -> Zones -> public, "mdns" should appear on the list on the right
- avahi is installed and running
mbologna marked this conversation as resolved.
Show resolved Hide resolved
- typically you can check this via systemd: `systemctl status avahi-daemon`
- Avahi is capable of resolving the host you are trying to reach: `avahi-resolve -n mbologna-uyuni.tf.local`
mbologna marked this conversation as resolved.
Show resolved Hide resolved
- mdns is configured in glibc's Name Server Switch configuration file

In `/etc/nsswitch.conf` you should see a `hosts:` line that looks like the following:
Expand All @@ -38,6 +39,15 @@ hosts: files mdns [NOTFOUND=return] dns
```
`mdns` (optionally suffixed with `4` for IPv4-only or `6` for IPv6-only) should be present in this line. If it is not, add it.

Starting with `nss-mdns` version 0.14.1, you also need to populate `/etc/mdns.allow` with:

```
.local.
.local
mbologna marked this conversation as resolved.
Show resolved Hide resolved
```

`mdns.allow` is required to [force all .local domains to be resolved regardless of label count or unicast SOA records](https://github.com/lathiat/nss-mdns/blob/master/README.md#etcmdnsallow).
mbologna marked this conversation as resolved.
Show resolved Hide resolved

## Q: how can I work around slowness in resolution of `tf.local` mDNS/Zeroconf/Bonjour/Avahi names?

If there is a 5-second delay on any name resolution (or ping) between Avahi hosts, a likely cause is that ipv6 is enabled on the VMs (that is the default setting) but the network is blocking ipv6 traffic.
Expand Down