software:dns-sd
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software:dns-sd [2020/06/26 20:14] – [DNS-Based Service Discovery] superwizard | software:dns-sd [2020/07/20 01:15] (current) – [Other Service Discovery Information] superwizard | ||
---|---|---|---|
Line 129: | Line 129: | ||
+ | ====== DNS-Based Service Discovery ====== | ||
+ | |||
+ | |||
+ | <WRAP center round box > | ||
+ | 11. Discovery of Browsing and Registration Domains (Domain Enumeration) | ||
+ | |||
+ | One of the motivations for DNS-based Service Discovery is to enable a | ||
+ | | ||
+ | | ||
+ | what services are available on that network, without any manual | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | This discovery is performed using DNS queries, using Unicast or | ||
+ | | ||
+ | |||
+ | b._dns-sd._udp.< | ||
+ | | ||
+ | r._dns-sd._udp.< | ||
+ | | ||
+ | | ||
+ | |||
+ | By performing PTR queries for these names, a client can learn, | ||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | Dynamic Update. | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | Sophisticated client applications that care to present choices of | ||
+ | domain to the user use the answers learned from the previous four | ||
+ | queries to discover the domains to present. | ||
+ | current applications browse without specifying an explicit domain, | ||
+ | allowing the operating system to automatically select an | ||
+ | appropriate domain on their behalf. | ||
+ | application that the " | ||
+ | allow the network administrator to communicate to the client | ||
+ | operating systems which domain(s) should be used automatically for | ||
+ | these applications. | ||
+ | |||
+ | </ | ||
+ | |||
+ | From: https:// | ||
==== DNS-Based Service Discovery ==== | ==== DNS-Based Service Discovery ==== | ||
Line 205: | Line 256: | ||
{{ : | {{ : | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
And Of Course you need A (AAAA) and PTR records | And Of Course you need A (AAAA) and PTR records | ||
Line 212: | Line 267: | ||
{{ : | {{ : | ||
+ | |||
+ | |||
+ | {{ : | ||
Line 251: | Line 309: | ||
Avahi also implements binary compatibility libraries that emulate Bonjour and the historical mDNS implementation Howl, so software made to use those implementations can also utilize Avahi through the emulation interfaces. | Avahi also implements binary compatibility libraries that emulate Bonjour and the historical mDNS implementation Howl, so software made to use those implementations can also utilize Avahi through the emulation interfaces. | ||
</ | </ | ||
+ | |||
+ | <WRAP center round box > | ||
+ | From: https:// | ||
+ | |||
+ | After my alterations, | ||
+ | |||
+ | < | ||
+ | <?xml version=" | ||
+ | < | ||
+ | < | ||
+ | <name replace-wildcards=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | The model information I’ve used, sets the icon to an XServe icon (see the screenshot above). You can determine the model text you need to broadcast for other icons by digging through the Plist at / | ||
+ | </ | ||
+ |
software/dns-sd.1593202480.txt.gz · Last modified: 2020/06/26 20:14 by superwizard