with the new zima version 1.7 i found a strange thing : I use adguard and I added 2 shortcuts in the local DNS names : zima and fritzbox with their corresponding local ip adresses (192.168. xxx.xxx)
After the update i cant reach my zima by using just zima as a dns name. i still can reach my fritzbox .
I can ping fritzbox and my mac will find it, I cant ping zima.
After I changed the dns name from only zima into zima.box it worked again, however if i use the name my zimabox doesnt show its local IP in the settings menu, if i reach it via its local ip adress it does.
@Antonius How do you configure the local host through AdGuard? In addition, if it is accessed through host, the system settings page only shows the host and will not display the ip address. In addition, Unknown has been adjusted later (it is expected that it will be solved in the next version)
yes and now that I replaced zima.box with zima (as it was originally) its all back to how it was before updating so its hard to say what caused that little trouble. on my win11 it used to work but it seems with the update its like this : ping zima =no , ping zima.box = ok.
I am used to add some names to my dns so I can reach them by that and never had issues with names that didnt have a .tld with , seems the missing .box makes the difference here
