Re: Clients Matching Multiple Views

2014-04-09 Thread Kevin Darcy
When you say "alternate zone", do you mean *schizophrenic* (i.e. some leaf-node names resolve to different RDATA between the versions), or do you mean only that the versions bear a subset/superset relation to each other, at least with respect to leaf nodes (SOA/NS records being a different matt

Re: Clients Matching Multiple Views

2014-04-09 Thread Jason Brandt
I faced a similar situation when setting up my servers. The way I handled it (correctly or not) was to built the zones in the internal view as master, and then the external view slaved to the internal master. That way you can simply update your internals, and the external side automatically popul

Re: Clients Matching Multiple Views

2014-04-09 Thread Steven Carr
On 9 April 2014 13:09, Mike Meredith wrote: > What I did in testing (and not very much at that) was to define the > zones twice with different file names. Seemed to work fine ... at least > the zone files and the journal files were created for both file names. BIND will allow you to configure it

Re: What if no root servers?

2014-04-09 Thread Chris Buxton
On Apr 9, 2014, at 12:02 AM, Dean Gibson (DNS Administrator) wrote: > I'm interested in a special use-case, where (say, in an emergency), access to > most of the Internet (and hence the root servers) is cut off. In this > situation, there is an emergency connected network consisting of severa

Re: Clients Matching Multiple Views

2014-04-09 Thread Mike Meredith
On Wed, 09 Apr 2014 12:05:07 +0300, Sotiris Tsimbonis may have written: > On 09/04/2014 11:14 πμ, Steven Carr wrote: > > That's not how views work. When you match a view then that's it, you > > don't continue to check other views. Thanks. As I suspected views select _clients_. It might be a handy

Re: Private & separate DNS domains

2014-04-09 Thread Joseph S D Yao
On 2014-04-08 07:35, Jason Brandt wrote: ... All of our Windows clients resolve through our Bind servers, and have no problems with any AD resources.  The only MSW machines that point to our AD DNS servers, are our DC's.  All clients will resolve just fine through BIND, so long as your zones are

Re: Clients Matching Multiple Views

2014-04-09 Thread Steven Carr
On 9 April 2014 10:05, Sotiris Tsimbonis wrote: > But when the zone is dynamic, this file "sharing" cannot be done between > views. > > Updates only match one zone, and are kept in memory (or .jnl). > So how would we make this work in dynamic zones? > Maybe we should have one view axfr from the ot

Re: Clients Matching Multiple Views

2014-04-09 Thread Sotiris Tsimbonis
On 09/04/2014 11:14 πμ, Steven Carr wrote: > On 9 April 2014 08:37, Mike Meredith wrote: >> Am I missing something obvious? Such as it should work, but I've >> somehow messed up? Or perhaps there's some option I've missed? Or am I >> out of luck? > > That's not how views work. When you match a vi

Re: Clients Matching Multiple Views

2014-04-09 Thread Steven Carr
On 9 April 2014 08:37, Mike Meredith wrote: > Am I missing something obvious? Such as it should work, but I've > somehow messed up? Or perhaps there's some option I've missed? Or am I > out of luck? That's not how views work. When you match a view then that's it, you don't continue to check other

Clients Matching Multiple Views

2014-04-09 Thread Mike Meredith
Hi! Using BIND 9.9 here ... I have a collection of secondaries with various zone masters (the majority BIND, some ActiveDirectory). Some of the secondary DNS servers are for internal use only; some are externally visible, but all are configured with a common configuration file. I have a need to