- Contact Us
Hello.. I've had the free account of dyndns with updater of running for a while. I use it with an iOS app that allows me to control sabdnzb on my computer. The host name in the ios is my dyndns hostname. It's been working great for the past year. I signed up with a VPN provider and downloaded the windows app. It connects to the VPN perfect and I'm able to access region restricted material as I intended. Problem is when the VPN is active I can't access my computer from the iOS app anymore. Dyndns updater sees my new IP provided by the VPN and gives me the IP address synced msg. If I turn off the VPN and wait 10mins I can connect remotely using the iOS app again. What am I doing wrong here? Any advice? Shouldn't dyndns sync with any IP it gets?
Answer by Cry Havok · Apr 10, 2013 at 04:54 PM
You've got 2 problems: 1. When the updater sees the new WAN IP, which is the IP of the VPN end point, it updates your hostname with that IP. Traffic is not port forwarded over the VPN to you, so you lose access 2. The VPN will likely re-route all traffic over the VPN, so any traffic that doesn't arrive on the VPN won't receive a reply (well, it will, but it'll come from a different IP so be ignored) In short, when the VPN is running you won't be able to remotely access the computer remotely. If the computer with sabdnzb isn't the one you need to VPN from then you may want to consider a second computer, or running the VPN from a virtual machine so that only it's traffic is impacted.
Answer by pixelrogue · Sep 03, 2015 at 01:39 PM
Slightly different version:
Need DynDNS to point to my Apple Time Capsule Router. Apple Time Capsule has an area specific for this function, however the 'update' does not seem to work as needed. Turns out that some are saying I need the DynDNS updater "also" running on a local machine. The ATC updates the local machine, which in turn updates the DynDNS helper app.
1) Seems like it works but a clunky work around. Happen to have an older computer around but in theory there would no more 'traditional' computer available and as such would need an updated IP without any computer.
2) The one computer uses a VPN. Understand that the VPN IP would not be accurate, but need the DynDNS to update for the ATC (which uses the proper IP), NOT the local computer which is using a VPN.
Screws everything up when the local computer should have nothing to do w/the IP going to the ATC. Seems like I am being forced to choose between using a VPN on a computer that has little to do w/the network, or DynDNS access to the network services.
Any help much appreciated.
DynDNS Wrong IP - Doesn't Work 1 Answer
Can't establish VPN 5 Answers
VPN + DynDNS + VNC 3 Answers