iOS app replaces IP of server with DNS name when added
It would appear that when you add a server by IP, a reverse DNS lookup is performed (or maybe the server just responds with its computer name?) and the IP of the saved Server is then replaced by the computer name/DNS name the next time you try and connect to the server. On the surface, this seems like a helpful feature, in the case of DHCP IPs changing, etc. But in most cases, I feel it would be beneficial to be able to add by IP address and just leave it saved as the IP address. The problem lies in the automatic/unavoidable reverse lookup and replacement of the IP with the DNS name. The DNS name "servername.local" works just fine when on the same network as the server, but as soon as I go off site and then VPN back in to my home network, those .local DNS names simply don't work (at least for me, with any router or VPN server I've used personally). However, the direct IP still totally works.
So to reproduce this issue, I disconnect from my local network and then VPN back in over cellular. I start with a fresh install of SecuritySpy iOS app, go to add a Server, after a moment when the app can't find one via Bonjour, I get the add new Server UI, I enter my server's LAN IP and click Continue, it finds it, connects and I can see my video feed. Yay! But if I close and reopen the app, or even just tap the server name up top and select the server again from the "Recent" list, it is unable to connect. If I "long press" on my server name under Recent, I get the little pop up action sheet showing the server name, and Connect, Delete, and Cancel buttons. On this pop up, I see that my server's IP (10.0.0.102:8000) has been replaced with the server's DNS name (servername.local:8000). So in order to reconnect to my camera, I have to delete the saved Server, and re-add again by IP, and then I can interact with it it once again, until I close the app, or hit the server list again. Rinse and repeat.
I obviously still think servers should be ABLE to be added by DNS name, however, I think that if the server is entered by IP, it should remain that way, as I think it was generally entered by IP for a reason. If someone adds by DNS name, or by Bonjour, then by all means, save it by the DNS name. But I think servers entered by IP should stay IP. As it is now, this is a pretty major usability issue, at least for me.
So to reproduce this issue, I disconnect from my local network and then VPN back in over cellular. I start with a fresh install of SecuritySpy iOS app, go to add a Server, after a moment when the app can't find one via Bonjour, I get the add new Server UI, I enter my server's LAN IP and click Continue, it finds it, connects and I can see my video feed. Yay! But if I close and reopen the app, or even just tap the server name up top and select the server again from the "Recent" list, it is unable to connect. If I "long press" on my server name under Recent, I get the little pop up action sheet showing the server name, and Connect, Delete, and Cancel buttons. On this pop up, I see that my server's IP (10.0.0.102:8000) has been replaced with the server's DNS name (servername.local:8000). So in order to reconnect to my camera, I have to delete the saved Server, and re-add again by IP, and then I can interact with it it once again, until I close the app, or hit the server list again. Rinse and repeat.
I obviously still think servers should be ABLE to be added by DNS name, however, I think that if the server is entered by IP, it should remain that way, as I think it was generally entered by IP for a reason. If someone adds by DNS name, or by Bonjour, then by all means, save it by the DNS name. But I think servers entered by IP should stay IP. As it is now, this is a pretty major usability issue, at least for me.
Comments
-
The problem here is that Bonjour names don't work over VPN. The solution is to turn off Bonjour in SecuritySpy, then the app won't use the Bonjour name, and will instead use the IP address that you have specified.
This is covered in the app user guide in the section Connecting Over a VPN.
In the next update to the app, we'll get it to remember the user-entered IP address, in addition to the other possible addresses (Bonjour and WAN) so that this overwriting of the IP address with the Bonjour address won't happen. -
That totally fixed it! I must have completely missed this section of the Users Guide. This 100% handles my concern. Just disabled the Bonjour option on the server and now it works as expected. Thanks so much.
-
Thank you for sharing this info. I have missed this one.
