<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Views are like any advanced technology
or technique in IT: if understood and used properly, they can be a
big benefit; poorly understood and/or implemented, they can create
a huge, unsupportable mess.<br>
<br>
I try to keep the number of views to a minimum, but given the
complexity I have to deal with, some of my named.conf's have as
many as 7 views (most of which are "temporary", since we're always
in the middle of migrating and/or sundowning something or
another).<br>
<br>
For some of us, virtual instances cost visible bucks from our
service provider, but views cost only extra support time, which is
lumped in with a bunch of other support costs, and is thus not
"visible". Sometimes it matters -- to beancounters -- whether
something is broken out as a line item or not...<br>
<br>
- Kevin<br>
<br>
On 1/2/2014 10:37 AM, Alan Clegg wrote:<br>
</div>
<blockquote
cite="mid:332EAC6B-899E-4497-B00B-577027A6D1A3@clegg.com"
type="cite">
<pre wrap="">
On Jan 2, 2014, at 9:19 AM, <a class="moz-txt-link-abbreviated" href="mailto:WBrown@e1b.org">WBrown@e1b.org</a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Use views
</pre>
</blockquote>
<pre wrap="">
Views +1
</pre>
</blockquote>
<pre wrap="">
When were views added to BIND? We started using using multiple servers in
BIND 4, and I don't recall views being available back then, but I didn't
configure the servers, just maintained the zones.
We're still using multiple servers for internal vs. external resolution.
</pre>
</blockquote>
<pre wrap="">
Views have been in bind “for all recent history”.
I’ve watched this thread and have been biting my tongue as long as I could.
I’m a proponent of separating servers and NOT using views, as any of you that have taken a class that I’ve taught will attest.
I’ve seen too many problems over the years that have been caused by incorrect maintenance of both data feeding the views and goofs in the mechanisms making sure that the correct view is made available to the correct slave servers (and clients).
With today’s hardware (virtualization, etc) it’s not very expensive to build out new servers. Separate the services and you remove lots of the little prickly points that will cause you pain as the complexity of your infrastructure grows (and as you hand off to the ‘next generation’ of maintainers).
I’m actually more a proponent of creating an architecture that doesn’t NEED differentiated data, but there aren’t a lot of places implementing DNS / naming structures on green-fields these days.
AlanC
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Please visit <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list
bind-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a></pre>
</blockquote>
<br>
</body>
</html>