Finally, the problem occurs the same way for all my WiFi-connected IoT devices (Tuya) that are registered with the same name in DNS. Even though I have defined a different name in /var/ipfire/dhcp/fixleases (both records are present)
[root@ipfire ~]# host wlan0
wlan0.pscar.dynu.com has address 192.168.10.77
wlan0.pscar.dynu.com has address 192.168.10.78
wlan0.pscar.dynu.com has address 192.168.10.178
wlan0.pscar.dynu.com has address 192.168.10.171
wlan0.pscar.dynu.com has address 192.168.10.172
wlan0.pscar.dynu.com has address 192.168.10.74
wlan0.pscar.dynu.com has address 192.168.10.174
wlan0.pscar.dynu.com has address 192.168.10.177
wlan0.pscar.dynu.com has address 192.168.10.76
wlan0.pscar.dynu.com has address 192.168.10.173
wlan0.pscar.dynu.com has address 192.168.10.176
wlan0.pscar.dynu.com has address 192.168.10.75
wlan0.pscar.dynu.com has address 192.168.10.82
wlan0.pscar.dynu.com has address 192.168.10.40
wlan0.pscar.dynu.com has address 192.168.10.79
When I deleted the corresponding records in the /var/ipfire/main/hosts file, I no longer had this problem.
I refound the unique name I defined in /var/ipfire/dhcp/fixleases for these devices.
And it has nothing to do with Microsoft !