Re: bind-users Digest, Vol 334, Issue 1

Kevin Darcy wrote: >I'm also wary of declaring the same range in multiple match lists (once >asserted, then negated everywhere else), since that means if the >numeric value of the range changes, you have multiple places to update, >and you could miss one. Here are two friends to help not miss

multiple internal views not working (RESOLVED)

All, thanks so much for your help in understanding match-clients in the view statement for zones. For historical purposes (and future searchers) this statement works: match clients { !10.x.5.0/24; 10.x.0.0/16; } doesn't serve .5, but serves everything else. Thank you Mr. Clegg (where do I s

Re: multiple internal views not working (requested conf files and logs)

Jeremy C. Reed wrote: > > Do you have anything to match here? By default, match-clients and > match-destinations default to matching all addresses (even not > "internal"). So when you reversed, the other view (dot5) would never > match and wouldn't work. > Hey Mr. Reed! Would this statement be e

Re: multiple internal views not working (requested conf files and logs)

Jeremy C. Reed wrote: It may be useful for you to show us what you tried (configurations and that it is restarted), how you tested, and any network traces and log files showing that it is not working. All, the 'dot5' view works great. The 'internal' view does not serve. If I reverse the view or

multiple internal views not working

technology company :-) Best, Paul Krash Sys/Sec/Net Administrator Exegy, Inc. pkr...@exegy.com This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The