VPNs to hosts resolving to multiple IPs often fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-pptp (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
pptp-linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
I tried to set up ipredator VPN via the network manager on ubuntu lucid lynx 10.04 64 bit and like a few other users as I could see on several forum, if I store password in keyring, it just don't try to connect.
Knowing that I disabled the keyring, and then was prompter for password, then it tried to connect but failed with a connection timed out error...
I had to put the IP adress of vpn.ipredator.se instead of the hostname for it to work...
I checked, it is not a problem with my ISP dns server:
doki@doki-
Server: 93.182.182.85
Address: 93.182.182.85#53
Non-authoritative answer:
Name: vpn.ipredator.se
Address: 93.182.146.2
Name: vpn.ipredator.se
Address: 93.182.147.2
Name: vpn.ipredator.se
Address: 93.182.148.2
Name: vpn.ipredator.se
Address: 93.182.149.2
Name: vpn.ipredator.se
Address: 93.182.150.2
Name: vpn.ipredator.se
Address: 93.182.151.2
Name: vpn.ipredator.se
Address: 93.182.152.2
Name: vpn.ipredator.se
Address: 93.182.153.2
Name: vpn.ipredator.se
Address: 93.182.164.2
Name: vpn.ipredator.se
Address: 93.182.179.2
Name: vpn.ipredator.se
Address: 93.182.180.2
Name: vpn.ipredator.se
Address: 93.182.181.2
Name: vpn.ipredator.se
Address: 93.182.185.2
Name: vpn.ipredator.se
Address: 93.182.186.2
Name: vpn.ipredator.se
Address: 93.182.187.2
Name: vpn.ipredator.se
Address: 93.182.188.2
Name: vpn.ipredator.se
Address: 93.182.189.2
Name: vpn.ipredator.se
Address: 93.182.190.2
Name: vpn.ipredator.se
Address: 93.182.130.2
Name: vpn.ipredator.se
Address: 93.182.132.2
Name: vpn.ipredator.se
Address: 93.182.133.2
So I don't know if it's a problem with network manager, or with pptp layer, but still, it doesn't seem to be able to resolve this hostname...
If you want me to run some tests/command or if you need more details, just ask :)
I'm able to reproduce this bug under Lucid.