I am running an Arch Linux server in my local network. It has avahi-daemon running on it to advertise some services (like a print server).

It has happened for the second time now that my server was not reachable anymore. After some investigation, I found out that its IPv4 address had been removed from the network interface, with these messages in the logs:

Feb 04 22:36:34 edeltraud avahi-daemon[389]: Withdrawing address record for on enp0s25.
Feb 04 22:36:34 edeltraud avahi-daemon[389]: Leaving mDNS multicast group on interface enp0s25.IPv4 with address
Feb 04 22:36:34 edeltraud avahi-daemon[389]: Interface enp0s25.IPv4 no longer relevant for mDNS.

The IP address is configured by DHCP using systemd-networkd. This is /etc/systemd/network/enp0s25.network:




What could be the reason for this?

  • WLAN? (wireless?)
    – Otheus
    Feb 5, 2016 at 15:03
  • No, cable._____
    – cdauth
    Feb 5, 2016 at 15:11
  • This is happening for me 24 hours after DHCP lease is established.So timing might be a good indicator of root cause.
    – mckenzm
    Oct 24, 2021 at 19:56

1 Answer 1


The message "Withdrawing address record" doesn't mean avahi is removing the IP address, it just means that avahi detected that the IP address has been removed, and is changing its internal state in response.

In other words, you need to look further; this isn't avahi's fault.

  • 2
    Interesting. Right now I cannot see if there were any other interesting log messages around the time the problem occurred, as the journal doesn’t reach that far back. I will try to investigate more when the problem appears again.
    – cdauth
    Mar 25, 2016 at 19:20
  • 1
    The problem occurred again, but I cannot find any hints before the avahi message: pastebin.com/xVx9Mbxg
    – cdauth
    Mar 28, 2016 at 17:58
  • 2
    Did you ever find a solution to this, I'm having the same issue on a Hyper-V guest Ubuntu 16.04 desktop, and as you described, the first relevant message is that "withdrawing" message. I can refresh the address (dhclient) but unsure why it's going missing. Mine is pure default on the network setup (and the hyperV switch is shared with my own desktop which didn't have a blip).
    – Linwood
    Nov 7, 2016 at 16:11
  • 1
    Never found a solution to it, fixed it by switching to a static IP address.
    – cdauth
    Nov 15, 2017 at 16:14
  • 1
    Running into this with WLAN, did you ever figure out a solution ?
    – jsaddwater
    Apr 14, 2021 at 11:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.