file can contain multiple service definitions which share the
same name. This is useful for publishing service data for
services which implement multiple protocols. (i.e. a printer
- implementing _ipp._tcp and _printer.tcp)</p> </description>
+ implementing _ipp._tcp and _printer._tcp)</p> </description>
<section name="XML Tags">
<option>
<p><opt><host-name></opt> The host name of the host that
- provides this service. This should be a mDNS resolvable host
- name. Please note that you need to specify a fully-qualified
- domain name (FQDN) here, i.e. .local is not appended! The host
- name needs not to be part of the domain specified in
- <opt><domain-name></opt>.</p>
+ provides this service. This should be a host that is
+ resolvable by multicast or unicast DNS. Please note that you
+ need to specify a fully-qualified domain name (FQDN) here,
+ i.e. .local is not appended implicitly! The host name doesn't
+ need to be part of the domain specified in
+ <opt><domain-name></opt>. See <manref name="avahi.hosts"
+ section="5"/> for more information how to publish additional
+ host name mappings.</p>
</option>
<option>
</section>
<section name="Authors">
- <p>The avahi developers <@PACKAGE_BUGREPORT@>; avahi is
+ <p>The Avahi Developers <@PACKAGE_BUGREPORT@>; Avahi is
available from <url href="@PACKAGE_URL@"/></p>
</section>
<section name="See also">
<p>
- <manref name="avahi-daemon" section="8"/>
+ <manref name="avahi-daemon" section="8"/>, <manref name="avahi.hosts" section="5"/>
</p>
</section>