On 26.07.2011 00:48, Kevin Darcy wrote:
Correct. That's the distinction which is typically made between a
DNS *forwarder* (which caches) and a DNS *proxy* (which doesn't).
As far as I know, BIND cannot be configured to be a DNS proxy.
On 26.07.11 11:11, Vbvbrj wrote:
But I don't want BIND as
2011/7/25 Vbvbrj :
> On 25.07.2011 10:15, Matus UHLAR - fantomas wrote:
This is how BIND is supposed to work. If you _need_ such setup, why
don't you setup your AD servers as recursive point clients directly to
them?
you can teoretically configure maximum cache time in BIN
On 26.07.2011 00:48, Kevin Darcy wrote:
Correct. That's the distinction which is typically made between a DNS
*forwarder* (which caches) and a DNS *proxy* (which doesn't). As far
as I know, BIND cannot be configured to be a DNS proxy.
But I don't want BIND as a proxy. )
Answers from its cache,
On Mon, Jul 25, 2011 at 7:53 PM, Vbvbrj wrote:
>
> I just can't for now move active directory's dns database to BIND.
>
You could use something much simpler like dnsmasq
(http://thekelleys.org.uk/dnsmasq/doc.html). Setting it up as a DNS
forwarder is a breeze, while you migrate DNS data away from
On 24.07.2011 18:40, Matus UHLAR - fantomas wrote:
This is how BIND is supposed to work. If you _need_ such setup,
why don't you setup your AD servers as recursive point clients
directly to them? you can teoretically configure maximum cache
time in BIND but that would be useless server.
On
In message <4e2de4bb.6050...@chrysler.com>, Kevin Darcy writes:
> On 7/24/2011 2:15 AM, Vbvbrj wrote:
> > options {
> > allow-transfer { none; };
> > recursion yes;
> > forward first;
> > forwarders { a.b.c.d; }; // Forward to providers dns.
> > };
> > zone "my_domain.com" IN {
> > type forwa
On 25.07.2011 10:15, Matus UHLAR - fantomas wrote:
This is how BIND is supposed to work. If you _need_ such setup, why
don't you setup your AD servers as recursive point clients directly
to them?
you can teoretically configure maximum cache time in BIND but that
would be useless server.
I can
On 7/24/2011 2:15 AM, Vbvbrj wrote:
options {
allow-transfer { none; };
recursion yes;
forward first;
forwarders { a.b.c.d; }; // Forward to providers dns.
};
zone "my_domain.com" IN {
type forward;
forward only;
forwarders { a.b.c.d; }; // Forward to Windows DNS.
};
I would like BI
On Jul 25, 2011, at 3:15 AM, Matus UHLAR - fantomas wrote:
>>> On 24.07.11 09:15, Vbvbrj wrote:
zone "my_domain.com" IN {
>
>> On 24.07.2011 18:40, Matus UHLAR - fantomas wrote:
>>> I would prefer not to using underscores in domain names. While they are
>>> allowed, they may cause some stu
On 24.07.11 09:15, Vbvbrj wrote:
zone "my_domain.com" IN {
On 24.07.2011 18:40, Matus UHLAR - fantomas wrote:
I would prefer not to using underscores in domain names. While they
are allowed, they may cause some stuff not to work.
Why do you have underscore here?
On 25.07.11 09:24, Vbvbrj w
On 24.07.2011 18:40, Matus UHLAR - fantomas wrote:
On 24.07.11 09:15, Vbvbrj wrote:
forwarders { a.b.c.d; }; // Forward to providers dns.
};
zone "my_domain.com" IN {
I would prefer not to using underscores in domain names. While they
are allowed, they may cause some stuff not to work.
Why
On 24.07.11 09:15, Vbvbrj wrote:
forwarders { a.b.c.d; }; // Forward to providers dns.
};
zone "my_domain.com" IN {
I would prefer not to using underscores in domain names. While they are
allowed, they may cause some stuff not to work.
Why do you have underscore here?
forwarders { a.b.c
options {
allow-transfer { none; };
recursion yes;
forward first;
forwarders { a.b.c.d; }; // Forward to providers dns.
};
zone "my_domain.com" IN {
type forward;
forward only;
forwarders { a.b.c.d; }; // Forward to Windows DNS.
};
I would like BIND to respond to local LAN like this:
13 matches
Mail list logo
