Lately I've noticed a constant flood of these entires in my syslog. ipv6 already disabled in my Unraid Network Settings (set to ipv4 only). Has anyone found a solution to either how to address these or disable them so they don't fill up logs? Seems my syslog would be almost empty without them. Thanks.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._ssh._tcp.local IN SRV 0 0 22 Unraid.local ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [_smb._tcp.local IN PTR Unraid._smb._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._smb._tcp.local IN TXT ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._smb._tcp.local IN SRV 0 0 445 Unraid.local ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [_sftp-ssh._tcp.local IN PTR Unraid._sftp-ssh._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._sftp-ssh._tcp.local IN TXT ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._sftp-ssh._tcp.local IN SRV 0 0 22 Unraid.local ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [_device-info._tcp.local IN PTR Unraid._device-info._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._device-info._tcp.local IN TXT "model=Xserve" ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:46:06 Unraid avahi-daemon[35430]: Record [Unraid._device-info._tcp.local IN SRV 0 0 0 Unraid.local ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:47:06 Unraid avahi-daemon[35430]: Record [Unraid._ssh._tcp.local IN SRV 0 0 22 Unraid.local ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:47:06 Unraid avahi-daemon[35430]: Record [Unraid.local IN A 192.168.0.168 ; ttl=120] not fitting in legacy unicast packet, dropping.

Oct 2 04:47:06 Unraid avahi-daemon[35430]: Record [_smb._tcp.local IN PTR Unraid._smb._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.

Oct 2 04:47:06 Unraid avahi-daemon[35430]: Record [Unraid._smb._tcp.local IN TXT ; ttl=4500] not fitting in legacy unicast packet, dropping.

Please post the diagnostics.

33 minutes ago, JorgeB said:

Please post the diagnostics.

Hi @JorgeB attached per your request. Really appreciate any insight you're able to provide. Thanks in advance.

unraid-diagnostics-20261002-1117.zip

Thanks for the diagnostics. These messages mean that Avahi cannot fit all the service-discovery records into a legacy unicast reply. This also happens over IPv4, so disabling IPv6 does not prevent it.

Your logs show bursts about once per minute, which suggests a device or application is repeatedly querying the server. The log filesystem is currently only 6% used.

To help identify the sender, run this in the Unraid terminal while the warnings occur:

tcpdump -pni br0 -nn -vv 'udp dst port 5353 and not udp src port 5353'

Let it run for about two minutes, then press Ctrl+C. Which device owns the source IP that repeats around the warning times? If you need help interpreting the output, post a few matching lines with addresses and hostnames replaced by consistent labels.

I recommend identifying that sender before disabling Avahi, since Avahi provides network service discovery.

Hi @JorgeB per your request, I was able to capture the attached logs from tcpdump using a docker container with tcpdump on host. Note these are all unique hardware devices and/or VLANs not running on my physical unraid instance. My unraid is on the 192.168.0.0/24 subnet:

Hardware 1:

192.168.0.1 my Unifi gateway

192.168.10.1 my Unifi CCTV gateway

192.168.20.1 my Unifi IoT gateway

192.168.30.1 my unifi guest gateway

Hardware 2:

192.168.0.193 Roon Rock media server

unraid_tcpdump.txt

Edited 14 hours ago14 hr by miles267

Thanks, this narrows it down. Your UniFi LAN gateway sends a large discovery query at 13:09:06 and again at 13:10:06. Both request SSH, SFTP, SMB, and device-info, the services listed in the Avahi warnings.

Similar queries also appear from the VLAN gateway addresses, which suggests mDNS forwarding. These packets do not need to originate from containers on Unraid.

The gateway queries are the strongest lead. However, we need syslog from the same capture period to confirm the connection.

Could you temporarily turn off UniFi’s mDNS Proxy, then watch the syslog and repeat the capture for about three minutes? Record the original setting first. Restore it afterward and check whether the warnings return. Leave Roon and Avahi running during this comparison.

This can temporarily interrupt device discovery across VLANs, including AirPlay, Chromecast, and printers.

Please also provide your UniFi Network version, gateway software version, and current mDNS Proxy mode. If the large queries continue with proxying disabled, we can investigate gateway discovery separately.