[dns-operations] anycasting axfr

Barry Raveendran Greene bgreene at senki.org
Wed Apr 19 20:45:06 UTC 2017

> I would guess that per-packet load balancing among different upstream
> providers in edge networks is going to be a bigger factor in failed root
> zone AXFRs than BGP topology changes in the core. I'd also guess that
> RIPE Atlas *anchors* are going to be on better managed networks and
> you'd be less likely to encounter that kind of load-balancing from Atlas
> anchors.

I’m trying to foresee any situation where a per packet load balancing issue would come up in this situation. Even with equal cost upstream exists, C & J would have 4 tuple selection on the path up (minimizing unnecessary asymmetric flows). Also, once you get a couple of BGP hops into the path, flows would stabilized to the anycasted NSID.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20170419/7692d315/attachment.sig>

More information about the dns-operations mailing list