<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Helvetica, Arial, sans-serif">We are running dnsdist
with anycast routing for over two years now with a customer base
of over 200K corporate and residential broadband subscribers. We
are using this for 6 different data center locations. We are
using dnsdist as load balancer with FRR (<a class="moz-txt-link-freetext" href="https://frrouting.org/">https://frrouting.org/</a>)
to run BGP with our IP gateways.</font></p>
<p><font face="Helvetica, Arial, sans-serif">Anycast is layer 3
routing. It is transparent of upper layers (UDP/TCP). Anycast
gives you IP reachability to the nearest node. </font><br>
</p>
<div class="moz-signature">Regards<br>
<b>Jahanzeb Arshad</b><br>
<br>
</div>
<div class="moz-cite-prefix">On 2/4/23 12:15, Lucas Rolff via
dnsdist wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3E185BBF-2461-412D-8B12-647EEEA54E68@lucasrolff.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
That's not correct, if that was the case, TCP applications in
general would not work in anycast setups, which obviously isn't
the case.
<div><br>
</div>
<div>It's correct that if you'd end up getting rerouted all of a
sudden, it would trigger a reset, but the application would
(likely) still succeed after establishing the TCP connection
again.</div>
<div><br>
</div>
<div>Running DNS (and accepting TCP queries) in an anycasted setup
is rather common :) I run a few of such setups.</div>
<div><br>
</div>
<div>
<div>
<div><br>
<blockquote type="cite">
<div>On 2 Apr 2023, at 14:08, Marco Mangione
<a class="moz-txt-link-rfc2396E" href="mailto:marco.mangione@gmail.com"><marco.mangione@gmail.com></a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div dir="ltr">becouse of split path routing, there are
2 or more anycast node and network load balancing
causes packet transmitted to the anycast address to
alternate between those nodes</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Il giorno dom 2 apr
2023 alle ore 08:59 Lucas Rolff <<a
href="mailto:lucas@lucasrolff.com"
moz-do-not-send="true"
class="moz-txt-link-freetext">lucas@lucasrolff.com</a>>
ha scritto:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">>
Because if traffic is forced on TCP, for example
with a TC=1, not everything could work correctly.<br>
<br>
Why not?<br>
<br>
> On 2 Apr 2023, at 13:55, Marco Mangione via
dnsdist <<a
href="mailto:dnsdist@mailman.powerdns.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">dnsdist@mailman.powerdns.com</a>>
wrote:<br>
> <br>
> Hi everyone,<br>
> I would like to open a conversation about a
dnsdist+pdns setup in anycast mode, therefore
multiple locations with multiple instances inside.<br>
> All OK if we talk about UDP, but what about
TCP? Has anyone had any experience?<br>
> <br>
> Because if traffic is forced on TCP, for
example with a TC=1, not everything could work
correctly.<br>
> <br>
> M1<br>
> _______________________________________________<br>
> dnsdist mailing list<br>
> <a href="mailto:dnsdist@mailman.powerdns.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">dnsdist@mailman.powerdns.com</a><br>
> <a
href="https://mailman.powerdns.com/mailman/listinfo/dnsdist"
rel="noreferrer" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">
https://mailman.powerdns.com/mailman/listinfo/dnsdist</a><br>
<br>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
dnsdist mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dnsdist@mailman.powerdns.com">dnsdist@mailman.powerdns.com</a>
<a class="moz-txt-link-freetext" href="https://mailman.powerdns.com/mailman/listinfo/dnsdist">https://mailman.powerdns.com/mailman/listinfo/dnsdist</a>
</pre>
</blockquote>
</body>
</html>