Annoying little thing with Blue access hostname resolution

[sec-con]

Stopped all the Blue today because wanted to start over and add the leases in “Devices on BLUE” again. Turns out a couple of hostnames are totally wrong and keep getting wrong. The IP and MAC and Remark I enter, or + Add, turns out ok, but not the hostnames on some devices.

Where is that stored, cause I really would like to clean it out and for it to show devices properly?

Example, and the most annoying entry:

My AP is most definitely not an Aqara device, but IPFire keeps pulling it in with that hostname. I do have an Aqara Hub, as described, but it does not have neither that MAC address nor that IP. This is the correct Aqara hub entry:

How can it be mixed up?

As previously mentioned, I cleaned out everything on Blue today, also restarted the IPFire appliance, but it still idoes that.

My AP also have a fixed entry in the DHCP table for Blue.

Any idea on how to correct this…?

[jon]

@sec-con

Where is that stored, cause I really would like to clean it out and for it to show devices properly?

try:

host 192.168.10.2
#  and
host 192.168.10.101

and share the results.

EDIT:

Get the Hostname From an IP Address in Linux | Baeldung on Linux

this might help clear the cache:

Dig on www.wikipedia.org fails, symptom of larger issues?

So your pathway is: LAN -> fw -> pi-hole -> DNS and return. If you do a dig +dnssec www.wikipedia.org @10.0.0.3 or dig +dnssec www.wikipedia.org from the FW the pathway according to your Domain Name System ends up being the same. The only difference is that the second one starts querying the local DNS cache first. This means you should probably flush the cache on the FW unbound-control -c /var/unbound/unbound.conf reload Not sure if that actually clears the DNS cache or just restarts unboun…

---

EDIT:

Unbound DNS Server Cache Control · abridge2devnull

[sec-con]

Can also be done in Windows with “nslookup [ipadress]”.

C:\Users\info>nslookup 192.168.10.2
Server:  fwipfire.homered.conram.it
Address:  192.168.1.1

Name:    Aqara-Hub-M2-AFE2.homered.conram.it
Address:  192.168.10.2

C:\Users\info>nslookup 192.168.10.101
Server:  fwipfire.homered.conram.it
Address:  192.168.1.1

Name:    Aqara-Hub-M2-AFE2.homered.conram.it
Address:  192.168.10.101

Is this the clear cache command in IPFire Console? Do we even use unbound?
Ah, yes, we seem to do: wiki.ipfire.org - DNS Forwarding

unbound-control -c /var/unbound/unbound.conf reload

So I tried to get in to that directory via IPFire SSH but that do not seem to work. Maybe console…nope same. Why can I not get in to the file structure?

In any case that unbound-control command did not work, could not find the conf file.

[root@fwipfire ~]# unbound-control -c /var/unbound/unbound.conf reload
[1686381083] unbound-control[31443:0] error: Could not open /var/unbound/unbound.conf: No such file or directory
[1686381083] unbound-control[31443:0] fatal error: could not read config file

[cfusco]

@sec-con

unbound-control -c /var/unbound/unbound.conf reload

unbound-control -c  /etc/unbound/unbound.conf reload

[sec-con]

[root@fwipfire ~]# unbound-control -c  /etc/unbound/unbound.conf reload
ok
[root@fwipfire ~]#

So what is the expected behaviour after that… ah

No hostname. Well, it might update itself I guess.

Thanks @cfusco and @jon