Re: DNS view "passthrough" and caching

In message <24234.1481320...@vindemiatrix.encs.concordia.ca>, Anne Bennett writes: > > Mark Andrews answers "Vladimir-M. Obelic" : > > > Use 'zone "zonename" { in-view "namename"; };' and have all zones > > that the view answers for be in that view. "in-view" was introduced > > in BIND 9.10.0

Re: DNS view "passthrough" and caching

Mark Andrews answers "Vladimir-M. Obelic" : > Use 'zone "zonename" { in-view "namename"; };' and have all zones > that the view answers for be in that view. "in-view" was introduced > in BIND 9.10.0. Configure the zone (master/slave) in the first > view it appears in. In that scenario, could

Re: DNS view "passthrough" and caching

Use 'zone "zonename" { in-view "namename"; };' and have all zones that the view answers for be in that view. "in-view" was introduced in BIND 9.10.0. Configure the zone (master/slave) in the first view it appears in. view "view1" { ... zone "example.com" { ...

DNS view "passthrough" and caching

Hello, I have two views configured, default (where the clients are first matched or denied) and view2 where only some clients should match (after being denied in default view match). Only one zone "zone.com" is defined in view2, whereas default view has all the other zones including "zone.com" a

Comments on Root Key Rollover impact on BIND users

You all are probably aware of the plans for rolling the root dnssec key in 2017. ICANN is trying to ensure this goes smoothly and we are of course looking for ways ISC can help. There is a draft blog post on the topic of the 2017 Root Key Rollover, kind of hidden on ISC’s web site here: https

Re: delegation broken after migrating to new BIND config

On Thu, Dec 8, 2016 at 11:09 PM, blrmaani wrote: > I migrated our bind resolvers to a new config (new named.conf) and I see > delegation broken. How do I trouble-shoot? > > - The resolvers (are slaves) and are authoritative for zone1.example.com > and example.com > - the resolvers forward queries