Skip Navigation Links | |
Exit Print View | |
Working With Naming and Directory Services in Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. Name Service Switch (Overview)
Multicast DNS Service Discovery
DNS and the Service Management Facility
How to Install the DNS Package
How to Create an rndc.conf File
How to Configure DNS Server Options
How to Run the DNS Service as an Alternative User
How to Troubleshoot DNS Server Startup Issues
How to Verify the DNS Configuration
Compilation Flags Used When BIND Was Built
4. Setting Up Oracle Solaris Active Directory Clients (Tasks)
Part II NIS Setup and Administration
5. Network Information Service (Overview)
6. Setting Up and Configuring NIS (Tasks)
9. Introduction to LDAP Naming Services (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP Naming Service (Reference)
The following sections explain how to enable multicast DNS (mDNS) and DNS service discovery. Also provided are examples of how to advertise resources for DNS service discovery.
For mDNS and DNS Service Discovery to function, mDNS must be deployed on all systems that are to participate in mDNS. The mDNS service is used to advertise the availability of services provided on the system.
For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.
# pkg install pkg:/service/network/dns/mdns
To be able to resolve local hosts, change the config/host property of the name-service/switch service to include mdns as a source. For example:
# /usr/sbin/svccfg -s svc:/system/name-service/switch svc:/system/name-service/switch> setprop config/host = astring: "files dns mdns" svc:/system/name-service/switch> select system/name-service/switch:default svc:/system/name-service/switch:default> refresh svc:/system/name-service/switch> quit
# svcadm enable svc:/network/dns/multicast:default
Enabling mDNS in this way ensures that your changes persist through upgrades and reboots. For more information, see the svcadm(1M) man page.
Check the mDNS service log, /var/svc/log/network-dns-multicast:default.log, for errors or messages.
You can use the dns-sd command as a network diagnosis tool, to browse and discover services, similar to how you would use the ping or traceroute command.
The dns-sd command is primarily for interactive use, mainly because its command-line arguments and its output format can change over time, which makes invoking it from a shell script unpredictable and risky. Additionally, the asynchronous nature of DNS service discovery (DNS-SD) does not easily lend itself to script-oriented programming.
For complete information, see the dns-sd(1M) man page. To incorporate the DNS service in applications, see the libdns-sd(3DNS_SD) man page.
The following are examples of advertising services using DNS service discovery.
Example 3-1 Advertising a Printing Service
The following command advertises the existence of LPR printing service on port 515 on a system called My Test, so that it will be available to DNS-SD compatible printing clients:
# dns-sd -R "My Test" _printer._tcp. . 515 pdl=application/postscript
For this registration to be useful, the LPR service must be available on port 515.
Example 3-2 Advertising a Web Page
The following command advertises a web page being served by an HTTP server on port 80 on the My Test system. The web page will appear on the Bonjour list in Safari and other DNS-SD compatible web clients.
# dns-sd -R "My Test" _http._tcp . 80 path=/path-to-page.html