<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I think you are pretty close. One detail that you appear to be missing are is in the linked document:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">server 10.0.1.1 {<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">/* Deliver notify messages to external view. */<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">keys { external-key; };<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">};<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Your slaves should have a similar statement in each view with the IP of the master and the relevant key for that view.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Two other things we have learned in deploying this:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">* It is helpful to change your allow-transfer section to be key-based per-view instead of IP based to save you from accidental zone transfers when other configuration errors are made.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">* The match-clients rule can be prepended with a key/!key set to prevent accidental communication on that view when using keys; e.g.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> match-clients {<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> # key matching rules<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> key admin-internal;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> !key admin-external;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> key slave-internal;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> !key slave-external;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> # ip/acl matching rules<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> internal-ips;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> };<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Mathew Eis<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Northern Arizona University<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Information Technology Services</span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">bind-users <bind-users-bounces@lists.isc.org> on behalf of Brian Pugh <project722@gmail.com><br>
<b>Date: </b>Thursday, August 18, 2016 at 7:15 PM<br>
<b>To: </b>"bind-users@lists.isc.org" <bind-users@lists.isc.org><br>
<b>Subject: </b>DNS views setup help<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I am running bind 9.8.2 on a pair of RHEL 6 DNS servers.. One server is the master, one is the slave. My goal is to setup 2 views so that our internal folks can resolve hostnames to internal IP's while still
allowing our external customers to resolve from the outside. Both of these servers are external facing and have only one public IP each. First of all I would like to know if what I am trying to achieve is even possible with my current setup. What we have are
internal users that are trying to access internal resources via a domain name that only exist in our external DNS. We do not have an internal zone for this domain or a inside DNS server that we can point them to in order to get a result for the query. So that
leaves us looking at views for the solution. <br>
<br>
To be more precise, this is what is happening now. <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Internal client > looks up host that's actually on the internal network but resolves to an external IP. The problem with this is 2 fold.
<o:p></o:p></p>
</div>
<p class="MsoNormal">1) DNS returns an external IP<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">2) Since the resource is internal, the traffic flow to the outside and back in happens on the same outside interface, which results in a hairpin, which we do not allow.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Now, what I was told is that a DNS view type solution would not be applicable to the hairpin. My understanding is that internal clients query the server already to get results for external IP, so if we had a
zone file in a view that had internal mappings, this would work and the internal user could access the resource since they are now being pointed to an internal IP.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So what I want to do is setup an "internal" view for the zone in question that points to a db file with the internal IP of that host, and an external view for everyone else.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">My questions is:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">1) Would DNS views work for my use case now that my server layout has been described?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">If so I need help in setting up TSIG because in my test lab everything seems to work except that on my slave server my zone in "view A" is being updated with the data from the master server from "view B". And
view B seems to be in sync on both servers, although it seems when I update zone files I have to restart instead of a reload to get the zones to update. Even then, that does not always work. There is a link I found online that says TSIG would be the solution
for this but it gives very little details on what the config is doing, so I do not know how to make TSIG work in my environment. This is the link I found:<br>
<br>
<a href="https://kb.isc.org/article/AA-00295/0/How-do-I-share-a-dynamic-zone-between-multiple-views-.html">https://kb.isc.org/article/AA-00295/0/How-do-I-share-a-dynamic-zone-between-multiple-views-.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Here are the relavent parts to my config as it stands now from the master.
<br>
<br>
acl internal {<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">1.2.3.4; // public IP coming from the inside users<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">};<br>
<br>
acl external {<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">5.6.7.8; // everyone else<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">9.10.11.12;; // everyone else<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">};<br>
<br>
view "insideview" {<br>
match-clients { internal; };<br>
<br>
zone"<a href="http://example.com">example.com</a>" IN {<br>
type master;<br>
file "/var/named/<a href="http://db.exampleinside.com">db.exampleinside.com</a>"; // this db file will be shown to the clients in the internal ACL and map back to internal IP's<br>
};<br>
};<br>
<br>
view "extview" {<br>
match-clients { external; };<br>
<br>
zone"<a href="http://example.com">example.com</a>" IN {<br>
type master;<br>
file "/var/named/<a href="http://db.exampleoutside.com">db.exampleoutside.com</a>";<br>
};<o:p></o:p></p>
</div>
<p class="MsoNormal">The conf from the slave is identical to the above. Can anyone help me by showing me what a TSIG config would look like for my environemnt?<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>