Hi, I'm not a OpenVPN developer but the support of SRV records is a good idea. A client configuration works without a predefined VPN server and port and whenever you move your VPN server to another location or network. Only a domain must defined that contain the right service record. I think it sound's very good or?!
-Markus On 12.08.2015 10:47, Gergely Czuczy wrote: > On 2015-08-11 21:19, Gert Doering wrote: >> Hi, >> >> On Tue, Aug 11, 2015 at 04:42:40PM +0200, Gergely Czuczy wrote: >>> I would like to ask some help, I'm looking at the OpenVPN source tree >>> from GitHub as I would like to see how much effort would it be me to add >>> SRV record support, as it has increasing demand these days (and really >>> makes sense, especially for enterprises). >> Can you elaborate a bit more on why SRV makes sense? To my naive thinking, >> the amount of stuff you have to put into the client profile anyway is >> so large (like CA cert etc) that the remaining gain is fairly small... > Sure thing. With a buzzwordish approach, I would say it enables more > enterprise-level configurations, > regarding redundancy, connection optimization and such things. > Technically speaking, with SRV records you are able to centrally manage > a set of servers where your clients > will be connecting to, including the order in which the clients should > > > -- > > Best regards, > Markus > > PGP-Key: http://freebsduser.eu/allgemein/pgp-public-key/ > PGP-Fingerprint: 949F 0510 E0C3 3B95 27A8 2EA2 38D9 56DE 2BA3 A0BA
0x2BA3A0BA.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
