nsd users - Jan 2020 - Seeking advice for deploying an anycast cluster

Hello,
> Of note, using NOTIFY doesn't seem possible, because if I start
> sending NOTIFYs to a constellation member, there doesn't seem to be a
> way to propagate that other constellation members.
This is usually solved by sending NOTIFY messages not to the anycasted
cluster address but to all the unique address of each cluster node instead.

--
Ond?ej Caletka

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3760 bytes
Desc: Elektronicky podpis S/MIME
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20200103/693e4598/attachment.bin>

The main issue I'm running into is I want to keep the primary's
interface to the world as simple as possible.   At maximum, two hosts
to communicate with.   So for that to work, I'd need to somehow
cluster my NSD instances together or I'd need some sort of proxy
server that can listen for incoming NOTIFYs and then distribute them
to the rest of the constellation.    I don't think any of the usual
suspects (nginx, haproxy, etc) have that capability out of the box.
Do they?

On Fri, Jan 3, 2020 at 3:49 AM Ond?ej Caletka via nsd-users
<nsd-users at lists.nlnetlabs.nl> wrote:
>
> Hello,
>
> > Of note, using NOTIFY doesn't seem possible, because if I start
> > sending NOTIFYs to a constellation member, there doesn't seem to
be a
> > way to propagate that other constellation members.
>
> This is usually solved by sending NOTIFY messages not to the anycasted
> cluster address but to all the unique address of each cluster node instead.
>
> --
> Ond?ej Caletka
>
>
> _______________________________________________
> nsd-users mailing list
> nsd-users at lists.nlnetlabs.nl
> https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users