On 02/22/2010 10:52:17 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > Someone may be relying on the behavior but, at the moment
> > or depending on present dns circumstances, does not have
> > multiple A records returned. In this case no warning will
> > be generated.
>
> The flip side of that coin is also valid I think.
>
> Consider independent configuration of VPN and DNS. Early errors would
> restrict VPN setup and possibly shipment until after DNS has been set
> up, while lazy evaluation allows DNS changes to happen later.
Right, but there's nothing to "restrict" because in this case we're
talking about a warning not an error; generating a warning that default
behavior will change in a future release. OpenVPN _should_
continue happily along its way no matter where
the warning is generated.
It's a pretty trivial point really, but may provide a template
for future changes.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
