<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi<br>
</p>
<div class="moz-cite-prefix">On 23/01/2020 04.16,
<a class="moz-txt-link-abbreviated" href="mailto:wbdumangeng@dilg.gov.ph">wbdumangeng@dilg.gov.ph</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1959375686.1290571.1579749374420.JavaMail.zimbra@dilg.gov.ph">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: arial, helvetica, sans-serif; font-size:
12pt; color: #000000">I have a question regarding the posture of
dnsdist as authoritative dns server facing public internet.
<div>How will be the design if you would put the dnsdist (load
balancer) infront the origin DNS servers?</div>
<div>I have two (2) internet facing authoritative DNS translated
from my firewall. Can I also do NAT on dnsdist</div>
<div>while the origin dns servers will be on private IP address?</div>
</div>
</blockquote>
<p>Short answer, yes.</p>
<p>Slightly longer answer, think of dnsdist more as a caching
proxy/load balancer than as a router. So you'd set up dnsdist to
listen for incoming queries and let dnsdist distribute the queries
among backend servers depending on your preferred load balancing
scheme. See also <a
href="https://dnsdist.org/guides/serverselection.html">https://dnsdist.org/guides/serverselection.html</a></p>
<p>For redundancy you'll probably also want at least 2 dnsdist
instances that can then sit in front of however many backends is
required to handle the load.</p>
<p>Best regards,</p>
<p>Jacob<br>
</p>
</body>
</html>