It's a pretty common failure for no matching hostname/IP/FQDN to be found on a host for an address in the config file. It would be useful if the troubleshooter could check that out and produce some diagnostics.
When there is a match (or matches), it should show what addresses matched what interfaces or the hostname:
Address matches for this host ... 2
ps.example.edu (Hostname)
ps.example.edu (eth0 IPv4 1.2.3.4)
1.2.3.4 (eth0 IPv4)
When there are no matches, it should dump out the hostname and a list of the interfaces and their addresses and FQDNs so the user can figure out what should match:
Address matches for this host ... None
This host's name is ps.example.edu
Interfaces on this host that did not match:
eth0:
IPv4 1.2.3.4 / ps.example.edu
IPv6 dead:beef::1 / psv6.example.edu
...etc...
It's a pretty common failure for no matching hostname/IP/FQDN to be found on a host for an address in the config file. It would be useful if the troubleshooter could check that out and produce some diagnostics.
When there is a match (or matches), it should show what addresses matched what interfaces or the hostname:
When there are no matches, it should dump out the hostname and a list of the interfaces and their addresses and FQDNs so the user can figure out what should match: