Hi Brian, Thanks for the quick reply!
> The only way I can get the second type of record permanently is by > putting it in /etc/hostname, which I believe is read by avahi-daemon. Ah, well now we're going into interesting territory. My /etc/hostname actually says 'cups4dhcp'[0]. I have set CUPS' ServerName to 'cups.pks.mpg.de' and assume this was the name used for the Bonjour record. Is there a way to debug the communication between avahi-daemon and cupsd that doesn't involve an actual debugger? I found avahi-daemon's '--debug' switch to be not that verbose. > Is your Debian testing a new install or an upgrade from Wheezy? My servers are all on 'testing' as in 'eternal testing'. :) That probably means the answer is "upgrade from Wheezy". I'll keep digging around... -Hagen [0] It's not quite easy to explain, but I'll try: I have *4* CUPS servers that serve different physical subnets (eg. LAN and WLAN). I chose the odd CUPS ServerName-setting in order to ensure that MacOS clients always see the same Bonjour name, instead of 'printer @ cups4dhcp.pks.mpg.de' when connected via cable and 'printer @ cups4wlan.pks.mpg.de' when in the WLAN. MacOS assumes they're different printers, so unhappiness quickly ensues. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org