Skip to main content

Setting Up DNS Discovery

Updated

If your network spans multiple IP subnets, you can use a DNS server to allow devices to automatically discover the DDM server.

Setting up DHCP

A DHCP server provides IP addresses and other bootstrap information for devices in a network. Many routers and switches come with DHCP functionality built in. Refer to the manual for your router, switch or DHCP server for configuration details.
 
When configuring DHCP specify the DNS server IP address and DNS domain name for the devices connecting to the DDM server as the first entry in the domain-search field. Dante devices will only use the first entry in the domain search path.

Important: Devices statically addressed in Dante Controller (or other programs) that do not include a domain search field cannot automatically discover the DDM server using DNS-SD.

Server Host (A) Record

The Host or “A” record will resolve the Dante Domain Manager Server’s IP address to a Fully Qualified Domain Name (FQDN). This allows users to type in the FQDN rather than the IP address when accessing Dante Domain Manager’s web browser interface or connecting to it from Dante Controller and will be referenced in the device and controller SRV records.

Important: If you want to change the DDM server’s hostname from the default ddm (i.e. to my-ddm) you’ll also need to update the hostname from the Dante Domain Manager Administration menu.

Setting up SRV/TXT Records

Dante devices and controllers can use DNS-SD (Service Discovery), when mDNS is not a viable option for discovery such as multi-subnet Dante systems or in a HA cluster. Each DNS-SD entry consists of an SRV record describing how to connect to the DDM Server and a TXT record with additional information (empty in this case).
 
The domain name in the SRV and TXT records must match the search domain(s) provided to clients (devices) by DHCP.

Controller Record

Record Name

InstanceServiceDomain
default._dante-ddm-c._tcpexample.com ( replace with DNS domain given to devices by DHCP)

SRV Record

  • TTL (time to live): 3600 (can be customized)
  • Class: IN
  • Weight, Priority: 0
  • Port: 8443
  • Target: ddm.example.com (replace with the FQDN of your DDM Server)

Text Record

  • Empty

Controller Record Example
default._dante-ddm-c._tcp.example.com. 3600 IN SRV 0 0 8443 ddm.example.comdefault._dante-ddm-c._tcp.example.com. 3600 IN TXT ""

(Replace string example.com with your DNS Domain and ddm.example.com with your DDM server’s FQDN)

Device Record

Record Name

InstanceServiceDomain
default._dante-ddm-d._udpexample.com ( replace with DNS domain given to devices by DHCP)

SRV Record

  • TTL (time to live): 3600 (can be customized)
  • Class: IN
  • Weight, Priority: 0
  • Port: 8000
  • Target: ddm.example.com (replace with the FQDN of your DDM Server)

Text Record

  • Empty

Controller Record Example
default._dante-ddm-d._udp.example.com. 3600 IN SRV 0 0 8000 ddm.example.comdefault._dante-ddm-d._udp.example.com. 3600 IN TXT ""

(Replace string example.com with your DNS Domain and ddm.example.com with your DDM server’s FQDN)

Related to

Related articles