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 check-response-ttl= Takes a boolean value ("yes" or "no"). If set to
38 "yes", an additional security check is activated: incoming IP packets
39 will be ignored unless the IP TTL is 255. Earlier mDNS specifications
40 required this check. Since this feature may be incompatible with newer
41 implementations of mDNS it defaults to "no". On the other hand it pro‐
42 vides extra security.
43 use-iff-running= Takes a boolean value ("yes" or "no"). If set to "yes"
45 avahi-daemon monitors the IFF_RUNNING flag bit which is used by some
46 (modern) network drivers to tell user space if a network cable is
47 plugged in (in case of copper ethernet), or the network card is associ‐
48 ated with some kind of network (in case of WLAN). If IFF_RUNNING is set
49 avahi-daemon will automatically announce its services on that network.
50 Unfortunately far too many network drivers do not support this flag or
51 support it in a broken way. Therefore this option defaults to "no".
52 enable-dbus= Takes either "yes", "no" or "warn". If set to "yes" avahi-
54 daemon connects to D-Bus, offering an object oriented client API. It is
55 only available if Avahi has been compiled with --enable-dbus in which
56 case it defaults to "yes". "warn" behaves like "yes", but the daemon
57 starts up even when it fails to connect to a D-Bus daemon. In addition,
58 if the connection to the D-Bus daemon is terminated we try to recon‐
59 nect. (Unless we are in a chroot() environment where this definitely
60 will fail.)
61 disallow-other-stacks= Takes a boolean value ("yes" or "no"). If set to
63 "yes" no other process is allowed to bind to UDP port 5353. This effec‐
64 tively impedes other mDNS stacks from running on the host. Use this as
65 a security measure to make sure that only Avahi is responsible for mDNS
66 traffic. Please note that we do no recommend running multiple mDNS
67 stacks on the same host simultaneously. This hampers reliability and is
68 a waste of resources. However, to not annoy people this option defaults
69 to "no".
70 allow-point-to-point= Takes a boolean value ("yes" or "no"). If set to
72 "yes" avahi-daemon will make use of interfaces with the POINTOPOINT
73 flag set. This option defaults to "no" as it might make mDNS unreliable
74 due to usually large latencies with such links and opens a potential
75 security hole by allowing mDNS access from Internet connections. Use
76 with care and YMMV!
77
79 enable-wide-area= Takes a boolean value ("yes" or "no"). Enable wide-
80 area DNS-SD, aka DNS-SD over unicast DNS. If this is enabled only
81 domains ending in .local will be resolved on mDNS, all other domains
82 are resolved via unicast DNS. If you want to maintain multiple differ‐
83 ent multicast DNS domains even with this option enabled we encourage
84 you to use subdomains of .local, such as "kitchen.local". This option
85 defaults to "yes".
86
88 disable-publishing= Takes a boolean value ("yes" or "no"). If set to
89 "yes", no record will be published by Avahi, not even address records
90 for the local host. Avahi will be started in a querying-only mode. Use
91 this is a security measure. This option defaults to "no"
92 disable-user-service-publishing= Takes a boolean value ("yes" or "no").
94 If set to "yes", Avahi will still publish address records and suchlike
95 but will not allow user applications to publish services. Use this is a
96 security measure. This option defaults to "no"
97 add-service-cookie= Takes a boolean value ("yes" or "no"). If set to
99 "yes" an implicit TXT entry will be added to all locally registered
100 services, containing a cookie value which is chosen randomly on daemon
101 startup. This can be used to detect if two services on two different
102 interfaces/protocols are actually identical. Defaults to "yes".
103 publish-addresses= Takes a boolean value ("yes" or "no"). If set to
105 "yes" avahi-daemon will register mDNS address records for all local IP
106 addresses. Unless you want to use avahi-daemon exclusively for browsing
107 it's recommended to enable this. If you plan to register local services
108 you need to enable this option. Defaults to "yes".
109 publish-hinfo= Takes a boolean value ("yes" or "no"). If set to "yes"
111 avahi-daemon will register an mDNS HINFO record on all interfaces which
112 contains information about the local operating system and CPU, which
113 might be useful for administrative purposes. This is recommended by the
114 mDNS specification but not required. For the sake of privacy you might
115 choose to disable this feature. Defaults to "yes."
116 publish-workstation= Takes a boolean value ("yes" or "no"). If set to
118 "yes" avahi-daemon will register a service of type "_workstation._tcp"
119 on the local LAN. This might be useful for administrative purposes
120 (i.e. browse for all PCs on the LAN), but is not required or recom‐
121 mended by any specification. Newer MacOS X releases register a service
122 of this type. Defaults to "yes".
123 publish-domain= Takes a boolean value ("yes" or "no"). If set to "yes"
125 avahi-daemon will announce the locally used domain name (see above) for
126 browsing by other hosts. Defaults to "yes".
127 publish-dns-servers= Takes a comma seperated list of IP addresses for
129 unicast DNS servers. You can use this to announce unicast DNS servers
130 via mDNS. When used in conjunction with avahi-dnsconfd on the client
131 side this allows DHCP-like configuration of unicast DNS servers.
132 publish-resolv-conf-dns-servers= Takes a boolean value ("yes" or "no").
134 If set to "yes" avahi-daemon will publish the unicast DNS servers spec‐
135 ified in /etc/resolv.conf in addition to those specified with publish-
136 dns-servers. Send avahi-daemon a SIGHUP to have it reload this file.
137 Defaults to "no".
138 publish-aaaa-on-ipv4= Takes a boolean value ("yes" or "no"). If set to
140 "yes" avahi-daemon will publish an IPv6 AAAA record via IPv4, i.e. the
141 local IPv6 addresses can be resolved using an IPv4 transport. Only use‐
142 ful when IPv4 is enabled with use-ipv4=true. Defaults to "yes".
143 publish-a-on-ipv6= Takes a boolean value ("yes" or "no"). If set to
145 "yes" avahi-daemon will publish an IPv4 A record via IPv6, i.e. the
146 local IPv4 addresses can be resolved using an IPv6 transport. Only use‐
147 ful when IPv6 is enabled with use-ipv6=true. Defaults to "no".
148
150 enable-reflector= Takes a boolean value ("yes" or "no"). If set to
151 "yes" avahi-daemon will reflect incoming mDNS requests to all local
152 network interfaces, effectively allowing clients to browse mDNS/DNS-SD
153 services on all networks connected to the gateway. The gateway is some‐
154 what intelligent and should work with all kinds of mDNS traffic, though
155 some functionality is lost (specifically the unicast reply bit, which
156 is used rarely anyway). Make sure to not run multiple reflectors
157 between the same networks, this might cause them to play Ping Pong with
158 mDNS packets. Defaults to "no".
159 reflect-ipv= Takes a boolean value ("yes" or "no"). If set to "yes" and
161 enable-reflector is enabled, avahi-daemon will forward mDNS traffic
162 between IPv4 and IPv6, which is usually not recommended. Defaults to
163 "no".
164
166 This section is used to define system resource limits for the daemon.
167 See setrlimit(2) for more information. If any of the options is not
168 specified in the configuration file, avahi-daemon does not change it
169 from the system defaults.
170 rlimit-as= Value in bytes for RLIMIT_AS (maximum size of the process's
172 virtual memory). Sensible values are heavily system dependent.
173 rlimit-core= Value in bytes for RLIMIT_CORE (maximum core file size).
175 Unless you want to debug avahi-daemon, it is safe to set this to 0.
176 rlimit-data= Value in bytes for RLIMIT_DATA (maximum size of the
178 process's data segment). Sensible values are heavily system dependent.
179 rlimit-fsize= Value for RLIMIT_FSIZE (maximum size of files the process
181 may create). Since avahi-daemon shouldn't write any files to disk, it
182 is safe to set this to 0.
183 rlimit-nofile= Value for RLIMIT_NOFILE (open file descriptors). avahi-
185 daemon shouldn't need more than 15 to 20 open file descriptors concur‐
186 rently.
187 rlimit-stack= Value in bytes for RLIMIT_STACK (maximum size of the
189 process stack). Sensible values are heavily system dependent.
190 rlimit-nproc= Value for RLIMIT_NPROC (number of process of user).
192 avahi-daemon forks of a helper process on systems where chroot(2) is
193 available. Therefore this value should not be set below 2.
194
196 The Avahi Developers <avahi (at) lists (dot) freedesktop (dot) org>;
197 Avahi is available from http://avahi.org/
198
200 avahi-daemon(8), avahi-dnsconfd(8)
201
203 This man page was written using xml2man(1) by Oliver Kurth.
204Manuals User avahi-daemon.conf(5)