Univention Bugzilla – Bug 34371
Add support for DNS-SD - Wide-Area Service Discovery - Bonjour/Zeroconf
Last modified: 2024-01-29 14:22:13 CET
DNS-SD (Service Discovery) is used by Bonjour/Zeroconf to automatically discover resources like printers. DNS-SD works around a common is of Bonjour, the limitation to the current subnet. I.e. printers are located in a network that's separated from the clients. These clients are not able to discover any printers by default. With DNS-SD the name server provides the missing functionality. Currently, UCS doesn't support DNS-SD, because it requires PTR records in a forward zone. More information is available here: - https://social.technet.microsoft.com/Forums/en-US/ad259e27-1077-4ebb-9008-5f8aef20bf17/setting-up-bonjour-service-proxy-on-ms-dns?forum=winserverNIS - http://www.dns-sd.org/ServerSetup.html - http://pig.made-it.com/cups-dns-sd.html This functionality was mentioned at Ticket #2014031821007345.
There is a workaround possible, even though it is not update-proof as the changes will get overwritten with an "ucr commit". Assuming using Samba as backend (ucr get dns/backend): Step 1 Edit named.conf.samba4 Add in section options{ }; : response-policy { zone "response-policy"; }; In file /etc/bind/local.conf.samba4 create the zone: zone "response-policy" { type master; file "/etc/bind/response-policy"; allow-query { none; }; }; Create the zone file /etc/bind/response-policy with the content as needed. i.e. as follows: $TTL 1H @ SOA LOCALHOST. hostmaster.example.org (1 1h 15m 30d 2h) NS LOCALHOST. ; define all internal domains to overwrite b._dns-sd._udp.example.org IN PTR pc-printer-discovery.example.org. lb._dns-sd._udp.example.org IN PTR pc-printer-discovery.example.org.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.