Ok, thanks for the clarification. That seemed to be what was going on, but I just wanted to confirm.
On Thu, 9 Dec 2021 at 12:58, libor.peltan <[email protected]> wrote: > > Yes, one remote is meant to be a single running DNS server. It can have > multiple addresses. When it gets notified via one of those addresses, > there is no point in contacting the other addresses belonging to the > same "remote". On the other hand, multiple remotes (= DNS servers) can > be configured for notify, if the primary has more secondaries. There is > no semantics for organizations and owners and such. You can perhaps add > comments (#) to your configuration file. > > /Libor > > Dne 09. 12. 21 v 18:53 Matthew Pounsett napsal(a): > > Just to clarify some semantics of the config format. > > > > Is each individual 'remote' ID considered to be a single server, > > regardless of the number of addresses it has? > > > > For the notify case, it looks like knot will send to each address in a > > remote ID in serial, and stop as soon as one replies. That suggests > > the above semantics, but I wanted to make sure I'm interpreting this > > behaviour correctly before I complicate my config by adding a lot more > > remotes. I am currently treating each remote as an organisation, > > lumping all of that organisation's servers together under a single ID. -- https://lists.nic.cz/mailman/listinfo/knot-dns-users
