Thanks, this looks like an interesting case away from the defaults.
>> If you really don't want that domain "myhost.local" published, and
also not "my-custom-name.local", then it can be disabled with
'publish-addresses=no'.
> This would also switch off publishing of my dynamic list.
I tested with my avahi 0.8-13ubuntu6 and CLI. With below config, it
won't publish the default host address record (A/AAAA) but it will still
publish any record that's explicitly added via the d-bus API.
This could be a service (SRV+TXT records, with a self-chosen host name
in the SRV record), or an address (A/AAAA record) using the "AddAddress"
in the entrygroup. Or an arbitrary record type using "AddRecord" (not
accessible via the avahi CLI).
This would enable any record types for any domain names of choice to be
published as a dynamic list. This is also useful to implement an mDNS proxy.
publish-addresses=no
publish-hinfo=no
publish-workstation=no
publish-domain=no
> The "consumer" of the mDNS domains is on the client side, in most/all
cases other machines or even OSes.
I was still wondering what the consumer would be looking for. Is it host
names for each of the Docker instances, i.e. encoded as A/AAAA records?
Or services (SRV+TXT records), one for each of the Dockers?
Or browsing/registration domains per Section 11 of RFC 6763, one for
each Docker encoded in a PTR record with name "b._dns-sd._udp.local." ?
For the first two cases there's "AddAddress" and "AddService". The last
case can be done with "AddRecord" most likely.
Esko
On 19-9-2025 18:07, Andreas wrote:
On 19/09/2025 14.07, Esko Dijk wrote:
Based on your example:
> Currently e.g. if my host is named "myhost" it publishes a dom1ain
"myhost.local".
Is "myhost" here the hostname of your computer (output of 'hostname'
command)? I assumed so.
It's a placeholder for the hostname of my computer. The real hostname
is different for each of my hosts.
The name "myhost.local" that gets published by default is the mDNS
host name (term as defined in RFC 6762 to be different from
computer's hostname).
Yes, and I'd like to not publish that (and also not a different static
mDNS host name). Just nothing.
This usually needs to be present, otherwise services can't be reached
on that host.
I'm publishing a dynamic list of domains, see below.
The option 'host-name' will change this name and make it independent
from the computer's hostname.
Doesn't matter, I would like to switch it off rather than renaming.
If you really don't want that domain "myhost.local" published, and
also not "my-custom-name.local", then it can be disabled with
'publish- addresses=no'.
This would also switch off publishing of my dynamic list.
I'm using avahi-daemon to publish a list of .local domains. That list
is dynamic and is changed with starting and stopping docker services.
Atm d-bus is used to add and remove domains to broadcast. Aside from
that dynamic list, no other domains shall be published.
I don't want to browse domains via avahi-daemon. The "consumer" of the
mDNS domains is on the client side, in most/all cases other machines
or even OSes.
--
IoTconsultancy.nl | Email/Teams: [email protected]
<mailto:[email protected]> | +31 6 2385 8339
