1avahi.service(5) File Formats Manual avahi.service(5)
2
6 avahi.service - avahi-daemon static service file
7
9 /etc/avahi/services/*.service
10
12 /etc/avahi/services/*.service are XML fragments containing static DNS-
13 SD service data. Every service file can contain multiple service defi‐
14 nitions which share the same name. This is useful for publishing ser‐
15 vice data for services which implement multiple protocols. (i.e. a
16 printer implementing _ipp._tcp and _printer._tcp)
17
19 <service-group> The document tag of avahi service files. Should contain
20 one <name> and one or more <service> elements.
21 <name replace-wildcards="yes|no"> The service name. If replace-wild‐
23 cards is "yes", any occurence of the string "%h" will be replaced by
24 the local host name. This can be used for service names like "Remote
25 Terminal on %h". If replace-wildcards is not specified, defaults to
26 "no".
27 <service protocol="ipv4|ipv6|any"> Contains the service information for
29 exactly one service type. Should contain one <type> and one <port> ele‐
30 ment. Optionally it may contain one <domain-name>, one <host-name>, any
31 number of <subtype> and any number of <txt-record> elements. The
32 attribute protocol specifies the protocol to advertise the service on.
33 If any is used (which is the default), the service will be advertised
34 on both IPv4 and IPv6.
35 <type> Contains the DNS-SD service type for this service. e.g.
37 "_http._tcp".
38 <subtype> Contains an additional DNS-SD service subtype for this ser‐
40 vice. e.g. "_anon._sub._ftp._tcp".
41 <domain-name> The domain name this service should be registered. If
43 omited defaults to the default domain of the avahi daemon. (probably
44 .local)
45 <host-name> The host name of the host that provides this service. This
47 should be a host that is resolvable by multicast or unicast DNS. Please
48 note that you need to specify a fully-qualified domain name (FQDN)
49 here, i.e. .local is not appended implicitly! The host name doesn't
50 need to be part of the domain specified in <domain-name>. See
51 avahi.hosts(5) for more information how to publish additional host name
52 mappings.
53 <port> The IP port number the service listens on.
55 <txt-record value-format="text|binary-hex|binary-base64"> DNS-SD TXT
57 record data. If value-format is "text", the value of the TXT record is
58 taken verbatim. If value-format is "binary-hex" then the value of TXT
59 record is decoded by taking pairs of characters after the "=" char and
60 interpreting them as the textual representation of the two-digit hexa‐
61 decimal number. Both uppercase and lowercase hexadecimal digits are
62 allowed. The 0x or 0X prefix is not allowed. This requires the length
63 of the value to be even. If value-format is "binary-base64" then the
64 value of TXT record is decoded with a base64 decoder. The character set
65 used is A-Za-z0-9+/. This requires the length of the value to be a mul‐
66 tiple of 4, with "=" as padding at the end. If value-format is not
67 specified, defaults to "text". Examples (all the values are decoded to
68 the string "value" without quotes):
69 <txt-record>key=value<txt-record>
71 <txt-record value-format="text">key=value<txt-record>
73 <txt-record value-format="binary-hex">key=76616c7565<txt-record>
75 <txt-record value-format="binary-base64">key=dmFsdWU=<txt-
77 record>
78
80 The Avahi Developers <avahi (at) lists (dot) freedesktop (dot) org>;
81 Avahi is available from http://avahi.org/
82
84 avahi-daemon(8), avahi.hosts(5)
85
87 This man page was written using xml2man(1) by Oliver Kurth.
88Manuals User avahi.service(5)