SOLUTION: Avahi-daemon startup broken in fresh F42 install

Fresh install of F42. Avahi daemon used to work fine before reinstalling F42. Now although avahi-daemon starts after a reboot, it’s broken. When it is restarted after boot with “systemctl restart avahi-daemon”. it then works fine and advertises its address successfully. I notice these lines in the systog after reboot:

Oct 10 22:16:56 KF6IIU-services avahi-daemon[891]: New relevant interface wlp1s0.IPv4 for mDNS.
Oct 10 22:16:56 KF6IIU-services avahi-daemon[891]: Registering new address record for 192.168.4.178 on wlp1s0.IPv4.
Oct 10 22:16:58 KF6IIU-services avahi-daemon[891]: Registering new address record for fdcc:2c9b:fabe:1:28e4:e83e:9de2:ea28 on wlp1s0.*.
Oct 10 22:16:58 KF6IIU-services avahi-daemon[891]: Withdrawing address record for fe80::538e:9b06:4fe8:539c on wlp1s0.  
However, when i restart the daemon, I get
Oct 10 22:18:16 KF6IIU-services avahi-daemon[1534]: Joining mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.4.178.
Oct 10 22:18:16 KF6IIU-services avahi-daemon[1534]: New relevant interface wlp1s0.IPv4 for mDNS.
Oct 10 22:18:16 KF6IIU-services avahi-daemon[1534]: Network interface enumeration completed.
Oct 10 22:18:16 KF6IIU-services avahi-daemon[1534]: Registering new address record for fdcc:2c9b:fabe:1:28e4:e83e:9de2:ea28 on wlp1s0.*.
Oct 10 22:18:16 KF6IIU-services avahi-daemon[1534]: Registering new address record for 192.168.4.178 on wlp1s0.IPv4.

I.E. that last IPV6 entry is never withdrawn. My conf file is configured for avahi to ignore IPV6 conpletely (relevant lines, changed from default):

use-ipv4=yes
use-ipv6=no
allow-interfaces=wlp1s0
deny-interfaces=enp2s0

[wide-area]
enable-wide-area=yes

[publish]
#disable-publishing=no
#disable-user-service-publishing=no
#add-service-cookie=no
publish-addresses=yes
publish-hinfo=no
publish-workstation=no
#publish-domain=yes
#publish-dns-servers=192.168.50.1, 192.168.50.2
#publish-resolv-conf-dns-servers=yes
#publish-aaaa-on-ipv4=yes
publish-a-on-ipv6=no

UPDATE: This was either due to a hyphen in the “transient hostname” assigned by the installation (highly unlikely) or that I did not have a “static” hostname assigned and only the “transient hostname” assigned by the installation.