Opened 8 years ago
Closed 8 years ago
#749 closed Bug / Defect (duplicate)
remote-random-hostname prevent connections when *.<hostname> domains doesn't resolve
| Reported by: | cypa | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | release 2.3.0 |
| Component: | Configuration | Version: | OpenVPN 2.3.2 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | remote-random-hostname dns |
| Cc: |
Description
openvpn client lost connection to server on m66.officeburg.ru due to remote-random-hostname option, because where is dns irregularity and client host cant resole random prefixed hostname,
actually on the server:
$ dig +short jl3wef.m66.officeburg.ru
5.172.23.43
62.33.152.80
$ dig +short m66.officeburg.ru
5.172.23.43
62.33.152.80
$
while on the client:
$ dig +short jl3wef.m66.officeburg.ru
$ dig +short m66.officeburg.ru
62.33.152.80
5.172.23.43
$
should openvpn client sometime resolve plain clear hostname m66.officeburg.ru, e.g. without random prefix?
Change History (4)
comment:1 Changed 8 years ago by
comment:2 Changed 8 years ago by
oops, seems random-remote-hostname totally broken in 2.3.2
Oct 6 10:15:23 busik2 ovpn-officeburg[8671]: RESOLVE: Cannot resolve host address: 62-0x5a7e9816bb08.33.152.80: Name or service not known
comment:3 Changed 8 years ago by
it is known and closed bug #143 https://community.openvpn.net/openvpn/ticket/143
still it is not fixed in current openvpn in Ubuntu 14.04
comment:4 Changed 8 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
if you need the plain hostname too, add a <connection> section wihtout remote-random.
The other but you are seeing is already fixed a long time ago (see #143)
shall setup this config to see long term behaviour ...