On Tue, 10 Aug 2010, Joseph S D Yao wrote:
> On Fri, Aug 06, 2010 at 10:43:01PM +0100, Tony Finch wrote:
> ...
> > As I understand it, BIND makes recursive queries to forwarding servers. If
> > the target is authoritative, you configure the zone as a stub. This is not
> > documented.
>
> I believe
On Tue, Aug 10, 2010 at 02:37:54PM -0400, Joseph S D Yao wrote:
...
> Then either it's not serving DNS or you haven't found the right buttons.
> What is it? Can you explain a bit more?
...
Sorry, in my hurry I didn't fast-forward through the thread. Glad that
it's working for you now.
--
/***
On Fri, Aug 06, 2010 at 10:43:01PM +0100, Tony Finch wrote:
...
> As I understand it, BIND makes recursive queries to forwarding servers. If
> the target is authoritative, you configure the zone as a stub. This is not
> documented.
I believe this is incorrect on both counts. In this form, BIND f
On Fri, Aug 06, 2010 at 10:05:01AM -0700, CLOSE Dave (DAE) wrote:
> Joseph S D Yao wrote:
>
> > If you have two forwarders, as you listed, your server will try to
> > forward first to one and then to the other. If it gets any answer at
> > all from one - even an error answer - it will not try the
I asked:
> My company has two internal name servers accessible to me. One (PUB) is
> the usual Internet-facing server than can resolve most internal and all
> public names. The other (PRIV) is a special purpose server that only
> resolves names in a special private domain. If I list both servers in
On 8/6/2010 7:28 PM, CLOSE Dave (DAE) wrote:
Sten Carlsen wrote:
I believe you could use forwarding to the internal server for each individual
name:
zone "HOST1" {
type forward;
forwarders{ private.domain.server.IP; };
}
This should do the trick but not elegant, not easy. I would
Sten Carlsen wrote:
> I believe you could use forwarding to the internal server for each individual
> name:
>
> zone "HOST1" {
>type forward;
>forwarders{ private.domain.server.IP; };
> }
>
> This should do the trick but not elegant, not easy. I would start hinting to
> management that
On 8/10/2010 9:16 AM, Tony Finch wrote:
On Mon, 9 Aug 2010, CLOSE Dave (DAE) wrote:
Based on suggestions here, I now have a named.conf file like this:
options { ... };
logging { ... };
zone "." IN { type forward; forwarders { PUB; }; forward only; };
zone "HOST1" { type for
On Mon, 9 Aug 2010, CLOSE Dave (DAE) wrote:
> Based on suggestions here, I now have a named.conf file like this:
>
>options { ... };
>logging { ... };
>zone "." IN { type forward; forwarders { PUB; }; forward only; };
>zone "HOST1" { type forward; forwarders { PRIV; }; };
>zone
On 2010-08-10 02:39, CLOSE Dave (DAE) wrote:
> Based on suggestions here, I now have a named.conf file like this:
>
>options { ... };
>logging { ... };
>zone "." IN { type forward; forwarders { PUB; }; forward only; };
>zone "HOST1" { type forward; forwarders { PRIV; }; };
>zon
Based on suggestions here, I now have a named.conf file like this:
options { ... };
logging { ... };
zone "." IN { type forward; forwarders { PUB; }; forward only; };
zone "HOST1" { type forward; forwarders { PRIV; }; };
zone "HOST2" { type forward; forwarders { PRIV; }; };
# PUB
On Thu, 5 Aug 2010, Lyle Giese wrote:
>
> zone "mydomain.com"{
> type forward;
> forward only;
> forwarders { ;}; };
>
> The priv server needs to be authorative(and probably master) for
> mydomain.com.
As I understand it, BIND makes recursive queries to forwarding servers. If
the target is authori
On 06/08/10 19:59, Kevin Darcy wrote:
> On 8/6/2010 1:05 PM, CLOSE Dave (DAE) wrote:
>> Joseph S D Yao wrote:
>>
>>
>>> If you have two forwarders, as you listed, your server will try to
>>> forward first to one and then to the other. If it gets any answer at
>>> all from one - even an error
On 8/6/2010 1:05 PM, CLOSE Dave (DAE) wrote:
Joseph S D Yao wrote:
If you have two forwarders, as you listed, your server will try to
forward first to one and then to the other. If it gets any answer at
all from one - even an error answer - it will not try the other.
So forwarding w
Joseph S D Yao wrote:
> If you have two forwarders, as you listed, your server will try to
> forward first to one and then to the other. If it gets any answer at
> all from one - even an error answer - it will not try the other.
So forwarding works exactly the same as listing both servers in
re
On Thu, Aug 05, 2010 at 06:03:34PM -0700, CLOSE Dave (DAE) wrote:
> My company has two internal name servers accessible to me. One (PUB) is
> the usual Internet-facing server than can resolve most internal and all
> public names. The other (PRIV) is a special purpose server that only
> resolves
Assuming your private domain is mydomain.com, in the named.conf for the
public server put:
zone "mydomain.com"{
type forward;
forward only;
forwarders { ;}; };
The priv server needs to be authorative(and probably master) for
mydomain.com.
In resolv.conf on the clients, you only need the pub serv
My company has two internal name servers accessible to me. One (PUB) is
the usual Internet-facing server than can resolve most internal and all
public names. The other (PRIV) is a special purpose server that only
resolves names in a special private domain. If I list both servers in
resolv.conf,
18 matches
Mail list logo
