1avahi-daemon.conf(5) File Formats Manual avahi-daemon.conf(5)
2
6 avahi-daemon.conf - avahi-daemon configuration file
7
9 /etc/avahi/avahi-daemon.conf
10
12 avahi-daemon.conf is the configuration file for avahi-daemon.
13
15 host-name= Set the host name avahi-daemon tries to register on the LAN.
16 If omited defaults to the system host name as set with the sethost‐
17 name() system call.
18 domain-name= Set the default domain name avahi-daemon tries to register
20 its host name and services on the LAN in. If omitted defaults to
21 ".local".
22 browse-domains= Set a comma seperated list of browsing domains (in
24 addition to the default one and those announced inside the default
25 browsing domain). Please note that the user may specify additional
26 browsing domains on the client side, either by setting
27 $AVAHI_BROWSE_DOMAINS to a list of colon seperated domains or by adding
28 them to the XDG config file ~/.config/avahi/browse-domains (seperated
29 by newlines).
30 use-ipv4= Takes a boolean value ("yes" or "no"). If set to "no" avahi-
32 daemon will not use IPv4 sockets. Default is "yes".
33 use-ipv6= Takes a boolean value ("yes" or "no"). If set to "no" avahi-
35 daemon will not use IPv6 sockets. Default is "yes".
36 allow-interfaces= Set a comma seperated list of allowed network inter‐
38 faces that should be used by the avahi-daemon. Other interfaces will be
39 ignored. If set to the empty list all local interfaces except loopback
40 and point-to-point will be used.
41 deny-interfaces= Set a comma seperated list of network interfaces that
43 should be ignored by avahi-daemon. Other not specified interfaces will
44 be used, unless allow-interfaces is set. This option takes precedence
45 over deny-interfaces.
46 check-response-ttl= Takes a boolean value ("yes" or "no"). If set to
48 "yes", an additional security check is activated: incoming IP packets
49 will be ignored unless the IP TTL is 255. Earlier mDNS specifications
50 required this check. Since this feature may be incompatible with newer
51 implementations of mDNS it defaults to "no". On the other hand it pro‐
52 vides extra security.
53 use-iff-running= Takes a boolean value ("yes" or "no"). If set to "yes"
55 avahi-daemon monitors the IFF_RUNNING flag bit which is used by some
56 (modern) network drivers to tell user space if a network cable is
57 plugged in (in case of copper ethernet), or the network card is associ‐
58 ated with some kind of network (in case of WLAN). If IFF_RUNNING is set
59 avahi-daemon will automatically announce its services on that network.
60 Unfortunately far too many network drivers do not support this flag or
61 support it in a broken way. Therefore this option defaults to "no".
62 enable-dbus= Takes either "yes", "no" or "warn". If set to "yes" avahi-
64 daemon connects to D-Bus, offering an object oriented client API. It is
65 only available if Avahi has been compiled with --enable-dbus in which
66 case it defaults to "yes". "warn" behaves like "yes", but the daemon
67 starts up even when it fails to connect to a D-Bus daemon. In addition,
68 if the connection to the D-Bus daemon is terminated we try to recon‐
69 nect. (Unless we are in a chroot() environment where this definitely
70 will fail.)
71 disallow-other-stacks= Takes a boolean value ("yes" or "no"). If set to
73 "yes" no other process is allowed to bind to UDP port 5353. This effec‐
74 tively impedes other mDNS stacks from running on the host. Use this as
75 a security measure to make sure that only Avahi is responsible for mDNS
76 traffic. Please note that we do not recommend running multiple mDNS
77 stacks on the same host simultaneously. This hampers reliability and is
78 a waste of resources. However, to not annoy people this option defaults
79 to "no".
80 allow-point-to-point= Takes a boolean value ("yes" or "no"). If set to
82 "yes" avahi-daemon will make use of interfaces with the POINTOPOINT
83 flag set. This option defaults to "no" as it might make mDNS unreliable
84 due to usually large latencies with such links and opens a potential
85 security hole by allowing mDNS access from Internet connections. Use
86 with care and YMMV!
87 cache-entries-max= Takes an unsigned integer specifying how many
89 resource records are cached per interface. Bigger values allow mDNS
90 work correctly in large LANs but also increase memory consumption.
91 clients-max= Takes an unsigned integer. The maximum number of concur‐
93 rent D-Bus clients allowed. If the maximum number is reached further
94 clients will be refused until at least one existing client disconnects.
95 objects-per-client-max= Takes an unsigned integer. The maximum number
97 of objects (entry groups, browsers, resolvers) that may be registered
98 per client at a time. If the maximum number is reached further object
99 creation will be refused until at least one object is freed.
100 entries-per-entry-group-max= Takes an unsigned integer. The maximum
102 number of entries (resource records) per entry group at a time. If the
103 maximum number is reached further resource records may not be added to
104 an entry group.
105
107 enable-wide-area= Takes a boolean value ("yes" or "no"). Enable wide-
108 area DNS-SD, aka DNS-SD over unicast DNS. If this is enabled only
109 domains ending in .local will be resolved on mDNS, all other domains
110 are resolved via unicast DNS. If you want to maintain multiple differ‐
111 ent multicast DNS domains even with this option enabled we encourage
112 you to use subdomains of .local, such as "kitchen.local". This option
113 defaults to "yes".
114
116 disable-publishing= Takes a boolean value ("yes" or "no"). If set to
117 "yes", no record will be published by Avahi, not even address records
118 for the local host. Avahi will be started in a querying-only mode. Use
119 this is a security measure. This option defaults to "no"
120 disable-user-service-publishing= Takes a boolean value ("yes" or "no").
122 If set to "yes", Avahi will still publish address records and suchlike
123 but will not allow user applications to publish services. Use this is a
124 security measure. This option defaults to "no"
125 add-service-cookie= Takes a boolean value ("yes" or "no"). If set to
127 "yes" an implicit TXT entry will be added to all locally registered
128 services, containing a cookie value which is chosen randomly on daemon
129 startup. This can be used to detect if two services on two different
130 interfaces/protocols are actually identical. Defaults to "no".
131 publish-addresses= Takes a boolean value ("yes" or "no"). If set to
133 "yes" avahi-daemon will register mDNS address records for all local IP
134 addresses. Unless you want to use avahi-daemon exclusively for browsing
135 it's recommended to enable this. If you plan to register local services
136 you need to enable this option. Defaults to "yes".
137 publish-hinfo= Takes a boolean value ("yes" or "no"). If set to "yes"
139 avahi-daemon will register an mDNS HINFO record on all interfaces which
140 contains information about the local operating system and CPU, which
141 might be useful for administrative purposes. This is recommended by the
142 mDNS specification but not required. For the sake of privacy you might
143 choose to disable this feature. Defaults to "yes."
144 publish-workstation= Takes a boolean value ("yes" or "no"). If set to
146 "yes" avahi-daemon will register a service of type "_workstation._tcp"
147 on the local LAN. This might be useful for administrative purposes
148 (i.e. browse for all PCs on the LAN), but is not required or recom‐
149 mended by any specification. Newer MacOS X releases register a service
150 of this type. Defaults to "yes".
151 publish-domain= Takes a boolean value ("yes" or "no"). If set to "yes"
153 avahi-daemon will announce the locally used domain name (see above) for
154 browsing by other hosts. Defaults to "yes".
155 publish-dns-servers= Takes a comma seperated list of IP addresses for
157 unicast DNS servers. You can use this to announce unicast DNS servers
158 via mDNS. When used in conjunction with avahi-dnsconfd on the client
159 side this allows DHCP-like configuration of unicast DNS servers.
160 publish-resolv-conf-dns-servers= Takes a boolean value ("yes" or "no").
162 If set to "yes" avahi-daemon will publish the unicast DNS servers spec‐
163 ified in /etc/resolv.conf in addition to those specified with publish-
164 dns-servers. Send avahi-daemon a SIGHUP to have it reload this file.
165 Defaults to "no".
166 publish-aaaa-on-ipv4= Takes a boolean value ("yes" or "no"). If set to
168 "yes" avahi-daemon will publish an IPv6 AAAA record via IPv4, i.e. the
169 local IPv6 addresses can be resolved using an IPv4 transport. Only use‐
170 ful when IPv4 is enabled with use-ipv4=true. Defaults to "yes".
171 publish-a-on-ipv6= Takes a boolean value ("yes" or "no"). If set to
173 "yes" avahi-daemon will publish an IPv4 A record via IPv6, i.e. the
174 local IPv4 addresses can be resolved using an IPv6 transport. Only use‐
175 ful when IPv6 is enabled with use-ipv6=true. Defaults to "no".
176
178 enable-reflector= Takes a boolean value ("yes" or "no"). If set to
179 "yes" avahi-daemon will reflect incoming mDNS requests to all local
180 network interfaces, effectively allowing clients to browse mDNS/DNS-SD
181 services on all networks connected to the gateway. The gateway is some‐
182 what intelligent and should work with all kinds of mDNS traffic, though
183 some functionality is lost (specifically the unicast reply bit, which
184 is used rarely anyway). Make sure to not run multiple reflectors
185 between the same networks, this might cause them to play Ping Pong with
186 mDNS packets. Defaults to "no".
187 reflect-ipv= Takes a boolean value ("yes" or "no"). If set to "yes" and
189 enable-reflector is enabled, avahi-daemon will forward mDNS traffic
190 between IPv4 and IPv6, which is usually not recommended. Defaults to
191 "no".
192
194 This section is used to define system resource limits for the daemon.
195 See setrlimit(2) for more information. If any of the options is not
196 specified in the configuration file, avahi-daemon does not change it
197 from the system defaults.
198 rlimit-as= Value in bytes for RLIMIT_AS (maximum size of the process's
200 virtual memory). Sensible values are heavily system dependent.
201 rlimit-core= Value in bytes for RLIMIT_CORE (maximum core file size).
203 Unless you want to debug avahi-daemon, it is safe to set this to 0.
204 rlimit-data= Value in bytes for RLIMIT_DATA (maximum size of the
206 process's data segment). Sensible values are heavily system dependent.
207 rlimit-fsize= Value for RLIMIT_FSIZE (maximum size of files the process
209 may create). Since avahi-daemon shouldn't write any files to disk, it
210 is safe to set this to 0.
211 rlimit-nofile= Value for RLIMIT_NOFILE (open file descriptors). avahi-
213 daemon shouldn't need more than 15 to 20 open file descriptors concur‐
214 rently.
215 rlimit-stack= Value in bytes for RLIMIT_STACK (maximum size of the
217 process stack). Sensible values are heavily system dependent.
218 rlimit-nproc= Value for RLIMIT_NPROC (number of process of user).
220 avahi-daemon forks of a helper process on systems where chroot(2) is
221 available. Therefore this value should not be set below 2.
222
224 The Avahi Developers <avahi (at) lists (dot) freedesktop (dot) org>;
225 Avahi is available from http://avahi.org/
226
228 avahi-daemon(8), avahi-dnsconfd(8)
229
231 This man page was written using xml2man(1) by Oliver Kurth.
232Manuals User avahi-daemon.conf(5)