Bug 34371 - Add support for DNS-SD - Wide-Area Service Discovery - Bonjour/Zeroconf
Add support for DNS-SD - Wide-Area Service Discovery - Bonjour/Zeroconf
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: DNS
UCS 5.0
Other Linux
: P5 enhancement with 2 votes (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-19 19:07 CET by Jan Christoph Ebersbach
Modified: 2021-10-29 15:00 CEST (History)
9 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2014031821007345, 2018121121001124, 2021102821000305
Bug group (optional): Roadmap discussion (moved)
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Christoph Ebersbach univentionstaff 2014-03-19 19:07:17 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.
Comment 1 Christian Völker univentionstaff 2018-12-12 10:06:58 CET
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.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:16:57 CET
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.