Weird hostname of HA OS machine

[TimoF (Timo)]

I am facing an issue with the hostname of my Homeassistant machine. I am running standard HA installation incl. OS v9.4, … on an odroid-H2.

I am facing the same issue as mentioned in this old unsolved github issue: github

Via Wireshark I capture the following:

14621	493.881418654	c806e693bf244f7ab33ce76691e5648d.local	224.0.0.251	MDNS	238	Standard query response 0x0000 SRV, cache flush 0 0 8123 c806e693bf244f7ab33ce76691e5648d.local AAAA, cache flush fe80::5228:278d:2a60:5311 AAAA, cache flush fd00::bbbd:837:2f6c:a548 A, cache flush 192.168.178.9 AAAA, cache flush 2a00:6020:####:####:####:####:202:6b9d

As far as I understand, something on my HA machine sends out a broadcast and promotes this cryptic hostname. This causes a wrong name e.g. in my Router. Sometimes access via homeassistant.{local,fritz.box} is also broken which is annoying.

I set the correct hostname “homeassistant” via UI and terminal "ha host options --hostname ‘homeassistant’ ". Both don’t change the behavior.

nslookup 192.168.178.9 return:

9.178.168.192.in-addr.arpa	name = c806e693bf244f7ab33ce76691e5648d.fritz.box.
9.178.168.192.in-addr.arpa	name = homeassistant.fritz.box.

Anyone an idea what sets and promotes this weird hostname? Maybe an addon?
Addons installed:

  name: Samba share
  version: 10.0.0
  name: Node-RED
  version: 14.0.0
  name: SSH & Web Terminal
  version: 13.0.0
  name: ESPHome
  version: 2022.12.3
  name: Studio Code Server
  version: 5.5.0
  name: InfluxDB
  version: 4.5.0
  name: Mosquitto broker
  version: 6.1.3
  name: Grafana
  version: 8.1.0
  name: MariaDB
  version: 2.5.1
  name: VLC
  version: 0.1.3

[WallyR (Wally)]

You probably have to look into the DNS and DHCP service.
My guess is that the DHCP service publish its leases to the DNS service and once the wrong name is in the DHCP service, then it keeps it until the record is purged, which will be once the lease time has run out and the IP pool have been cycled around. This might which again might never happen in a home network, since there are usually not enough device to make the IP pool cycle.

[t0mw3]

Happens also here with a Debian Docker-Compose Installation.
I think this is caused by a (default-config) activated Zeroconf in Home Assistant (multicast HA-uuid as a hostname).
My solution is to set the hostname in the FritzBox (Select the host in the Home Network list). Then the host has two identities (hostname with Home Assistant uuid and the expected hostname). You can prove it on the HA host with the shell command
host <ipaddr>.
I hope this helps others as well.

[marlemion]

I am running into this weird problem and cannot find a solution. It worked beforehand (since years now).

Now I get:

nslookup -type=PTR 192.168.178.33
Server:         192.168.178.1
Address:        192.168.178.1#53
 
33.178.168.192.in-addr.arpa     name = 586a19a58fbd4f8ab9559d3648b1619d.fritz.box.
33.178.168.192.in-addr.arpa     name = homeassistant.fritz.box.

nslookup homeassistant.fritz.box
Server:         192.168.178.1
Address:        192.168.178.1#53

** server can't find homeassistant.fritz.box: NXDOMAIN

nslookup 586a19a58fbd4f8ab9559d3648b1619d.fritz.box.
Server:         192.168.178.1
Address:        192.168.178.1#53

Name:   586a19a58fbd4f8ab9559d3648b1619d.fritz.box
Address: 192.168.178.33

This is very annoying in particular as I have not changed anything.

In HA, settings → system → network, the hostname option is gone!

It appears HA introduces something bad in view of the hostname setting in one of the last update. Can somebody confirm/help out? The solution proposed above does not work, as I have already set the hostname in the fritzbox.