id	summary	reporter	owner	description	type	status	milestone	component	resolution	keywords	cc
273	No unicast resolution if avahi is started before network is configured	jwelsh	lennart	"If avahi-daemon starts before /etc/resolv.conf is configured by dhcp, it will not resolve any requests via unicast DNS (e.g. for wide-area DNS-SD). If I do avahi-daemon -r it will reload resolv.conf (via the chroot helper I assume) and succeed. Perhaps resolv.conf could be added to the inotify watch list?

I'm using gentoo and avahi-daemon is usually started before DHCP is acquired. On Debian it seems ok normally but I can reproduce by ifdown / restart avahi / ifup. 

I'd imagine this is a worse problem for laptops using networkmanager or some such."	defect	closed	Avahi 0.6.26	avahi-daemon	wontfix