Actions
Bug #2579
closed
Update script fails to parse multiple DNS entries for OpenVPN properly. (1.2.3 -> 2.0)
Status:
Closed
Priority:
Low
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
08/07/2012
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
Description
If you use multiple DNS entries in 1.2.3, you are required to semicolon separate them to work properly.
In 2.0, there are multiple fields for different DNS entries.
During the upgrade, the multiple entries aren't parsed out to the several fields, but rather squished into one entry which doesn't work under the new OpenVPN setup. (No DNS is pushed to clients)
Separating the DNS entries into several fields manually is a workaround.
Updated by
Actions