VPN fails to resolve new server address

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect to openvpn server on dynamic IP address (server is using dyndns DNS 
alias)
2. Change server IP address by restarting ISP connection (ISP assigns new IP 
address and dyndns alias is updated to new address). Note that dyndns uses a 
very short 'lifetime' for DNS records to prevent caching by clients)
3. Notice that openvpn on android fails to reconnect and fails to resolve the 
new IP address.

What is the expected output? What do you see instead?

openvpn on linux/windows will resolve the new IP address automatically when 
reconnecting. this behaviour doesn't appear to work in android. Possibilities 
are that the openvpn client is not resolving the new IP address (and simply 
tries to connect to the last known IP address). 

While openvpn was continually retrying connection to the 'stale' IP address, I 
used a terminal in android to ping the DNS alias and it resolved to the correct 
(new) IP address - meaning that the DNS entry is not being cache within the 
operating system itself.

What version of the product are you using?
0.4.7

Which Android phone are you using?
HTC Desire

Which firmware version are you using?
2.2 Froyo (T-Mod / LeeDroid 2.2b)

Please provide any additional information below.

Original issue reported on code.google.com by marc.mar...@gmail.com on 19 Oct 2010 at 5:04

• Merged into: #21

[GoogleCodeExporter]

after reading issue #21 I investigated whether this is due to the 'Use VPN DNS' 
setting (which was enabled). I turned off this setting and restarted the VPN 
tunnel and tested again with the same result.

Original comment by marc.mar...@gmail.com on 19 Oct 2010 at 5:20

[GoogleCodeExporter]

Try to add some of this commands to your client.ovpn
persist-key
persist-remote-ip
resolv-retry infinite
With those I did manage to reconnect sometimes changing from 3g to wifi. But I 
still face failures. I don't know if in the server side something can be done 
to improve this or playing with the client.ovpn will fix the issue completly. 
I still in the process of trying some other commands to see how they work.
By the way, I'm with Desire HD, ROM Revolution HD 5.1.7, iptables version 1.4.7 
on top of the ROM. VPN-Settings from market with the fix on links as per:
ln -s /system/xbin/ifconfig /system/xbin/bb/ifconfig
ln -s /system/xbin/route /system/xbin/bb/route
ln -s /system/xbin/busybox /system/xbin/ifconfig

Original comment by ea7...@gmail.com on 24 May 2011 at 8:55

[GoogleCodeExporter]

Original comment by friedrich.schaeuffelhut on 28 Dec 2011 at 11:52

• Changed state: Duplicate