"Addon/App" container network issues

hi all. I have a HAOS running in a VM on my proxmox box. Its been running for ages and generally I don’t have that many issues, apart from this one problem that seems to come and go.

Basically I have an issue where the supervisor apps start having problems with the network stack, as in they are unable to get onto the network. The only way to resolve is a reboot of the whole VM that HA is running in. Its like a random container that the supervisor is running will just fail to get network access. It doesn’t look like all apps get affected either.

I can tell when this starts occuring because the frigate addon no longer is able to talk to my frigate server and the video feeds go blank, yet if I open a new browser tab and go straight to the frigate server, I can see it is running fine.

I have three specific apps that highlight this issue…

  • Frigate Proxy - Cameras in HA no longer can be seen, so I have to go directly to the frigate server webpage, not via HA

  • Zabbix Agent - The agent no longer is reportying to my zabbix server so I make the assumption that the HA box has crashed, but it hasn’t because I can open up HA fine.

  • Zigbee2MQTT - z2m can no longer connect to my SLZB-06 even though the stick is up and running fine.

How the hell do I even debug this? To me its something odd going on with Supervisor.

I had a look at the host logs, and can see the following every 2 hours. Nothing should be changing… no cable is being pulled.

2026-03-23 12:07:57.940 homeassistant systemd[1]: Started Hostname Service.
2026-03-23 12:07:57.955 homeassistant systemd[1]: Starting Time & Date Service...
2026-03-23 12:07:57.977 homeassistant systemd-timesyncd[1627822]: Network configuration changed, trying to establish connection.2026-03-23 12:07:57.940 homeassistant systemd[1]: Started Hostname Service.
2026-03-23 12:07:57.955 homeassistant systemd[1]: Starting Time & Date Service...
2026-03-23 12:07:57.977 homeassistant systemd-timesyncd[1627822]: Network configuration changed, trying to establish connection.

I think my issues are related to…

My network DNS is home.local and I think this is what is conflicting here. It works for a while, but then the DNS resolver container seems to shit the bed and then it all stops working