I found a workaround this problem. Check my git https://github.com/WillyWeiss/-Avahi-daemon-withdraws-address-record-/blob/master/README.md
I just a simple bash that check for a valid IP Address on a given card. If the IP is not found then 'dhclient' will be called on that given interface(card) It is working by default on eth0 but you can add more cards in the script. Just read the readme in the git above. Hope it helps. Prove of functionality: Sep 24 16:47:40 MyHostName rngd[395]: stats: Entropy starvations: 0 Sep 24 16:47:40 MyHostName rngd[395]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us Sep 24 16:47:46 MyHostName avahi-daemon[380]: Withdrawing address record for 192.168.0.13 on eth0. Sep 24 16:47:46 MyHostName avahi-daemon[380]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.13. Sep 24 16:47:46 MyHostName avahi-daemon[380]: Interface eth0.IPv4 no longer relevant for mDNS. Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPREQUEST for 192.168.0.13 on eth0 to 255.255.255.255 port 67 Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPACK of 192.168.0.13 from 192.168.0.1 Sep 24 16:47:47 MyHostName avahi-daemon[380]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.13. Sep 24 16:47:47 MyHostName avahi-daemon[380]: New relevant interface eth0.IPv4 for mDNS. Sep 24 16:47:47 MyHostName avahi-daemon[380]: Registering new address record for 192.168.0.13 on eth0.IPv4. Sep 24 16:47:47 MyHostName dhclient[4487]: bound to 192.168.0.13 -- renewal in 41664 seconds. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
