ASIMount@ZWO Yes I know that, my scenario is when the AM5 wifi is connected to my local network. My router will then assign a certain IP address to the hand controller (192.168.0.44 for instance), and when I enter that address in the field, it works great :
![](https://bbs.astronomy-imaging-camera.com/assets/files/2023-11-02/1698947122-916945-image.png)
I can also access the hand controller with the DNS "amh.5" (for instance, in the browser, or with a ping to confirm the IP):
![](https://bbs.astronomy-imaging-camera.com/assets/files/2023-11-02/1698947494-138382-image.png)
But I won't be able to connect to my AM5 via its DNS on the ASCOM interface, because it wants an IP address :
![](https://bbs.astronomy-imaging-camera.com/assets/files/2023-11-02/1698947564-509806-image.png)
It's a little be frustrating because it seems to be a really easy update to just allow any network DNS instead of just an IP, and it would greatly improve my use of the mount 🙂