<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Affan,<div><br></div><div>As dns is mostly stateless, you can certainly use things like VRRP, CARP or other protocols for an HA setup. Theirs is no dnsdist specific documentation on this because there's nothing "special" about dnsdist that VRRP/CARP needs to know. You could use any documentation for your VRRP / CARP / other protocol out there.</div><div><br></div><div>That being said, I have two big remarks to make.</div><div><br></div><div>A lot of people who have a need to achieve this failover capability, prefer to do it BGP based, as you have a bit more control and predictability over the BGP protocol than for instance with VRRP(e). If you would launch a search query for "bgp dnsdist" or "bgp dns", you'll find a ton of blogposts and howtos. Again here: these blogposts talk about the BGP implementation, not soo much about dnsdist.</div><div><br></div><div>My second big remark is that dns has high-availability mechanisms built in: most TLDs require a minimum of 2 nameservers to be specified for authoritative name servers, all decent DNS client implementations allow you to specify more than one resolver. If you do this correctly, you'll achieve dns high-availability out of the box. Yes, there might be latency issues and you might get a higher rate of complaints from your users, but if those hiccups are short, the DNS protocol itself will fail over.</div><div><br></div><div>Kind Regards,</div><div><br></div><div>Frank</div><div><br></div><div><br><div>
<div><meta charset="UTF-8"><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Frank Louwers<br>PowerDNS Certified Consultant @ Kiwazo.be</div></div></div>
</div>
<div><br><blockquote type="cite"><div>On 10 Sep 2023, at 16:31, Affan Basalamah via dnsdist <dnsdist@mailman.powerdns.com> wrote:</div><br class="Apple-interchange-newline"><div>Hello,<div dir="auto"><br></div><div dir="auto">I want to know if it’s possible to setup dnsdist as two server and configured with first hop redundancy protocol such as VRRP (Keepalived on Linux, CARP on FreeBSD), so dnsdist can operate as highly available as possible, at least in fail over mode. </div><div dir="auto"><br></div><div dir="auto">If it’s possible, I haven’t seen the examples on the official dnsdist documentation. Can someone point me to any document or other references?</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Best regards,</div><div dir="auto">Affan </div>
_______________________________________________<br>dnsdist mailing list<br>dnsdist@mailman.powerdns.com<br>https://mailman.powerdns.com/mailman/listinfo/dnsdist<br></div></blockquote></div><br></div></div></div></body></html>