Module Description

The mDNS module allows managing services over IP network using mDNS for resolving hostnames and DNS-SD for publishing and discovering services. The main entry point for that is the MDNSAdmin interface, under which OSGi services with specific implementation can be registered.

Feature Set

The mDNS module provides the following features:

Bosch.IO mDNS API
- Provides a common abstraction over the different platform and stack-specific implementations with the following main features:
  - Allows discovery and listing of mDNS nodes according mDNS Type and mDNS Service.
  - Provides event-based notifications via OSGi Event Admin when new type and/or service is added, resolved or removed from the mDNS network.
  - Provides means for exporting mDNS services with certain type and concrete mDNS TXT Record.
Bosch.IO mDNS API implementation based on JmDNS:
- Implements Bosch.IO mDNS API on top of JmDNS library.
mDNS Pluggable Commands:
- Provides the following functionality using Bosch.IO mDNS API:
  - List of cached service instances
  - Detailed information for service instance according its service name and service type
  - Forces scan of the network for certain mDNS services with certain service type
  - Forces resolving of service instance with certain service name and service type
  - Subscription for fully qualified service types, for example, _http._tcp.local. The events must be printed in the console. In addition, the unsubscribe must be implemented too.

Module Dependencies

OSGi Framework – The OSGi runtime is required for the module to operate.

Known Issues and Limitations

Port 5353 must be opened for both incoming and outgoing communication.
Sometimes after a service is removed, SERVICE RESOLVED events are still fired due to broken or misunderstood functionality in the underlying JmDNS implementation.

Licensing Information

Check JmDNS 3.4.1 of the Third-Party Licenses: External Modules