On 22-Apr-10, at 12:49 AM, Karl O. Pinc wrote:
On 04/21/2010 09:13:35 AM, Toby Thain wrote:
On 21-Apr-10, at 11:49 PM, Richard Monk wrote:
I had an issue come up where the clients were getting DNS entries
in
the
reverse order the server sends them when using the client.up
contrib
On 22-Apr-10, at 12:49 AM, Karl O. Pinc wrote:
On 04/21/2010 09:13:35 AM, Toby Thain wrote:
On 21-Apr-10, at 11:49 PM, Richard Monk wrote:
I had an issue come up where the clients were getting DNS entries
in
the
reverse order the server sends them when using the client.up
contrib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/04/10 17:55, Richard Monk wrote:
> On 04/21/2010 11:51 AM, Davide Brini wrote:
>> as a matter of fact, there's a new version of that script (and client.down
>> as
>> well) in the git testing tree, which should fix your problem as it just uses
On 04/21/2010 11:51 AM, Davide Brini wrote:
> as a matter of fact, there's a new version of that script (and client.down as
> well) in the git testing tree, which should fix your problem as it just uses
> the DNS servers in the order they're sent from the server. See here for more
> details:
>
On Wednesday 21 Apr 2010 14:49:13 Richard Monk wrote:
> I had an issue come up where the clients were getting DNS entries in the
> reverse order the server sends them when using the client.up contrib
> script. Since the DNS servers on our system are in order from
> closest->farthest network wise
On 04/21/2010 10:49 AM, Karl O. Pinc wrote:
>> Have you considered a local caching DNS with forwarding?
>
> I don't see how this will solve the problem.
> What if the closest _is_ a local caching DNS with forwarding
> to the next farthest out? You still want all the DNS servers
> available in
On 04/21/2010 09:13:35 AM, Toby Thain wrote:
>
> On 21-Apr-10, at 11:49 PM, Richard Monk wrote:
>
> > I had an issue come up where the clients were getting DNS entries
> in
>
> > the
> > reverse order the server sends them when using the client.up
> contrib
> > script. Since the DNS servers
On 21-Apr-10, at 11:49 PM, Richard Monk wrote:
I had an issue come up where the clients were getting DNS entries in
the
reverse order the server sends them when using the client.up contrib
script. Since the DNS servers on our system are in order from
closest->farthest network wise from the
I had an issue come up where the clients were getting DNS entries in the
reverse order the server sends them when using the client.up contrib
script. Since the DNS servers on our system are in order from
closest->farthest network wise from the VPN server, having them
backwards caused some
