Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
multicastdns [2007/06/03 13:19] – FredrikLindbergmulticastdns [2019/02/01 09:46] (current) – add to CategoryProject MateuszPiotrowski
Line 1: Line 1:
 ====== Multicast DNS ====== ====== Multicast DNS ======
  
-[http://www.multicastdns.org/ Multicast DNS (mDNS)] is a part of Zero Configuration Networking (Zeroconf) and provides the ability to address hosts using DNS-like names without the need of an existing (unicast), managed DNS server.+[[http://www.multicastdns.org/|Multicast DNS (mDNS)]] is a part of Zero Configuration Networking (Zeroconf) and provides the ability to address hosts using DNS-like names without the need of an existing (unicast), managed DNS server.
  
 The project is divided into two phases each with a set of sub-projects. The sub-projects in phase 1 is more or less The project is divided into two phases each with a set of sub-projects. The sub-projects in phase 1 is more or less
 listed in the order they will be implemented in (they depend on each other), sub-projects in phase 2 is not listed listed in the order they will be implemented in (they depend on each other), sub-projects in phase 2 is not listed
 in the same order as they will be implemented. in the same order as they will be implemented.
-Focus and priority will initially be on phase 1 only. 
  
-[:%%MulticastDNS%%/SOCproposal:Original %%SoC%% proposal]+  * [[MulticastDNS/Quickstart|Quick start]] - If you want to play with it. 
 +  * [[MulticastDNS/SOCproposal|Original SoC proposal]] 
 + 
 +A public mercurial repository with snapshots is available at http://hg.h3q.net/mdns
  
 ===== Phase 1 ===== ===== Phase 1 =====
 ==== Multicast DNS responder (mdnsd) ==== ==== Multicast DNS responder (mdnsd) ====
 +Status: Feature complete, requires testing and bugfixing.
 +
 This is the core responder daemon, performs multicast dns queries on behalf of clients and acts as This is the core responder daemon, performs multicast dns queries on behalf of clients and acts as
 a unified cache to all clients. a unified cache to all clients.
 Provides the ability to announce its own mdns records onto the network. Provides the ability to announce its own mdns records onto the network.
-[:%%MulticastDNS%%/responderd:Details]+ 
 +[[MulticastDNS/responderd|Details]]
  
 ==== Client API (libmdns) ==== ==== Client API (libmdns) ====
 +Status: Working
 +
 Provides a easy programming interface to the client side of responderd. Provides a easy programming interface to the client side of responderd.
 Privileges operations include addition/removal of self-claimed records, while non-privileged operations Privileges operations include addition/removal of self-claimed records, while non-privileged operations
Line 23: Line 30:
  
 ==== NSS module ==== ==== NSS module ====
-Uses libmdns and hooks into the name-service switch system to expose mdns aware-versions of +Status: Complete 
-gethostby{name,name2,addr} and similar functions. + 
-Configuration file /etc/mdns.conf (similar to resolv.conf) will control the search space. Default would be .local+Uses libmdns and hooks into the name-service switch system to expose mdns aware-versions of name lookup functions. 
 +Implements gethostby{name,name2,addr}, getaddrinfo and ghby{addr,name} (used by getipnodeby{name,addr} and getnameinfo). 
 +Configuration file /etc/mdns.conf (similar to resolv.conf) controld the search space. Default is .local and private ip-addresses.
  
 ==== Command line utility ==== ==== Command line utility ====
 +Status: Working
 +
 Utility named mdns (or similar) to provide basic host name lookup for debugging purposes and Utility named mdns (or similar) to provide basic host name lookup for debugging purposes and
 to provide a way to dynamically add and remove self-claimed mdns records. to provide a way to dynamically add and remove self-claimed mdns records.
 +It currently supports resolving names, add/remove/list names and resources and view/flush cache,
 +its feature set is in sync with features provided by libmdns.
  
 ===== Phase 2 ===== ===== Phase 2 =====
 ==== Service Discovery integration ==== ==== Service Discovery integration ====
-(Need to do some more thinking on this part). +Status: Not started (Open task) 
-The current idea is to have a separate library say, libsd which would expose a common API to both + 
-multicast based service discovery and wide-area service discovery (unicast).+Create an application to do both multicast (libmdns) and unicase service discovery. 
 +The previous idea with a separate library is probably overkill at the moment.
  
 ==== Avahi library wrapper (mdns_compat_avahi) ==== ==== Avahi library wrapper (mdns_compat_avahi) ====
-A wrapper library around libmdns (and possibly libsd) to allow avahi-aware applications to work with mdns_responderd.+Status: Not started (Open task) 
 + 
 +A wrapper library around libmdns to allow avahi-aware applications to work with mdns_responderd.
 It seems most normal avahi consumers performs queries through d-bus so this compat library will probably It seems most normal avahi consumers performs queries through d-bus so this compat library will probably
 mimic this interface. The api avahi-core exposes will probably not be covered. mimic this interface. The api avahi-core exposes will probably not be covered.
  
 ==== dns_sd library wrapper (mdns_compat_dns_sd) ==== ==== dns_sd library wrapper (mdns_compat_dns_sd) ====
 +Status: Not started (Open task)
 +
 A wrapper library around libmdns (and possibly libsd) to allow apple dns_sd-aware applications to work with mdns_responderd. A wrapper library around libmdns (and possibly libsd) to allow apple dns_sd-aware applications to work with mdns_responderd.
 The API header (dns_sd.h) is released by Apple under a BSD-license. The API header (dns_sd.h) is released by Apple under a BSD-license.
 +
 +----
 +
 +{{tag>Project}}
  
  • multicastdns.1180876778.txt.gz
  • Last modified: 2007/06/03 13:19
  • by FredrikLindberg