Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dnsextd(8) [osx man page]

dnsextd(8)						    BSD System Manager's Manual 						dnsextd(8)

dnsextd -- BIND Extension Daemon SYNOPSIS
dnsextd is a daemon invoked at boot time, running alongside BIND 9, to implement two EDNS0 extensions to the standard DNS protocol. dnsextd allows clients to perform DNS Updates with an attached lease lifetime, so that if the client crashes or is disconnected from the net- work, its address records will be automatically deleted after the lease expires. dnsextd allows clients to perform long-lived queries. Instead of rapidly polling the server to discover when information changes, long-lived queries enable a client to indicate its interest in some set of data, and then be notified asynchronously by the server whenever any of that data changes. dnsextd has no user-specifiable command-line argument, and users should not run dnsextd manually. SEE ALSO
mDNS(1) mDNSResponder(8) For information on Dynamic DNS Update, see RFC 2136 "Dynamic Updates in the Domain Name System (DNS UPDATE)" For information on Dynamic DNS Update Leases, see For information on Long-Lived Queries, see BUGS
dnsextd bugs are tracked in Apple Radar component "mDNSResponder". HISTORY
The dnsextd daemon first appeared in Mac OS X 10.4 (Tiger). Darwin June 2, 2019 Darwin

Check Out this Related Man Page

mDNSResponder(8)					    BSD System Manager's Manual 					  mDNSResponder(8)

mDNSResponder -- Multicast and Unicast DNS daemon SYNOPSIS
mDNSResponder (also known as mdnsd on some systems) is a daemon invoked at boot time to implement Multicast DNS and DNS Service Discovery. On Mac OS X 10.6 (Snow Leopard), mDNSResponder is also the system-wide Unicast DNS Resolver. mDNSResponder listens on UDP port 5353 for Multicast DNS Query packets. When it receives a query for which it knows an answer, mDNSResponder issues the appropriate Multicast DNS Reply packet. mDNSResponder also performs Unicast and Multicast DNS Queries on behalf of client processes, and maintains a cache of the replies. mDNSResponder has no user-specifiable command-line argument, and users should not run mDNSResponder manually. LOGGING
There are several methods with which to examine mDNSResponder's internal state for debugging and diagnostic purposes. The syslog(1) logging levels map as follows: Error - Error messages Warning - Client-initiated operations Notice - Sleep proxy operations Info - Informational messages By default, only log level Error is logged. A SIGUSR1 signal toggles additional logging, with Warning and Notice enabled by default: % sudo killall -USR1 mDNSResponder Once this logging is enabled, users can additionally use syslog(1) to change the log filter for the process. For example, to enable log lev- els Emergency - Debug: % sudo syslog -c mDNSResponder -d A SIGUSR2 signal toggles packet logging: % sudo killall -USR2 mDNSResponder A SIGINFO signal will dump a snapshot summary of the internal state to /var/log/system.log: % sudo killall -INFO mDNSResponder OPTIONAL ARGUMENTS
mDNSResponder accepts the following optional arguments: -AlwaysAppendSearchDomains Append search domains for multi-labeled Partially Qualified Domain Name as well as single-labeled Partially Quali- fied Domain Name. This argument is not recommended because of the extra DNS traffic it generates and its adverse effect on battery life. -NoMulticastAdvertisements Prevent the system from advertising Bonjour services via Multicast DNS. To cause mDNSResponder to run with these optional arguments when it launches on OS X 10.11 (El Capitan) and later, set the AlwaysAppendSearchDomains or NoMulticastAdvertisements boolean keys to true in /Library/Preferences/ and reboot. FILES
/usr/sbin/mDNSResponder /Library/Preferences/ INFO
For information on Multicast DNS, see For information on DNS Service Discovery, see For information on how to use the Multicast DNS and the DNS Service Discovery APIs on Mac OS X and other platforms, see For the source code to mDNSResponder, see BUGS
mDNSResponder bugs are tracked in Apple Radar component "mDNSResponder". HISTORY
The mDNSResponder daemon first appeared in Mac OS X 10.2 (Jaguar). Also available from the Darwin open source repository (though not officially supported by Apple) are mDNSResponder daemons for other plat- forms, including Microsoft Windows, Linux, FreeBSD, NetBSD, Solaris, and other POSIX systems. Darwin June 1, 2019 Darwin
Man Page

Featured Tech Videos