Paul Wouters wrote:
> On Tue, 14 Nov 2017, Jacques Latour wrote:
>
> > Personally, I like a mix of #3 and #1, on a regular basis poll the entire
> > zone for changes, and have a mechanism to listen to child notifications
> > for urgent changes.
>
> Agreed.
Yes.
> > _AND_ remember, the preferred
On Tue, 14 Nov 2017, Jacques Latour wrote:
Personally, I like a mix of #3 and #1, on a regular basis poll the entire
zone for changes, and have a mechanism to listen to child notifications
for urgent changes.
Agreed.
_AND_ remember, the preferred method by far is to submit a DS/DNSKEY
record
Parental synchronization is inevitable so we would be better to find the
best way to make it happen. I think there are 3 plausible methods to do
the synchronization.
1. Child Notification: Child sends NOTIFY to a predefined parental
destination. The parent then polls the child zone for changes an
Evan Hunt wrote:
>
> In the present context, I was only suggesting this method be used for
> NOTIFY, not UPDATE -- to signal the parent that it should poll the child
> for CDS/CDNSKEY. (I guess CSYNC could be included in the mix as well,
> though, for updating NS and glue.)
Yes.
> I would sugge
On 14/11/2017 01:37, Evan Hunt wrote:
> On Tue, Nov 14, 2017 at 09:16:43AM +1100, Mark Andrews wrote:
>> Remember the draft was designed to handle ALL record updates to the
>> parent zone after being approved by the registrar in a unified manner.
>> NS, DS, A, DNAME, , TXT, CNAME, etc. This i
On Tue, Nov 14, 2017 at 09:16:43AM +1100, Mark Andrews wrote:
> Remember the draft was designed to handle ALL record updates to the
> parent zone after being approved by the registrar in a unified manner.
> NS, DS, A, DNAME, , TXT, CNAME, etc. This isn’t restricted to DS
> records.
In the pr
> On 14 Nov 2017, at 5:45 am, Edward Lewis wrote:
>
> On 11/13/17, 13:30, "DNSOP on behalf of Evan Hunt" behalf of e...@isc.org> wrote:
>
>> Mark's idea to push updates to the parent instead of relying on polling used
>> a SRV query to identify the correct recipient of an UPDATE:
>>
>> ...
Evan Hunt wrote:
...
Mark's idea to push updates to the parent instead of relying on polling
used a SRV query to identify the correct recipient of an UPDATE:
https://tools.ietf.org/html/draft-andrews-dnsop-update-parent-zones-04
The same trick could be used to find the right NOTIFY target.
On 11/13/17, 13:30, "DNSOP on behalf of Evan Hunt" wrote:
>Mark's idea to push updates to the parent instead of relying on polling used a
>SRV query to identify the correct recipient of an UPDATE:
>
>...draft-andrews-dnsop-update-parent-zones-04...
This would mean then signing all the SRV
On Mon, Nov 13, 2017 at 03:19:23PM +, Tony Finch wrote:
> It seems to me that a reasonable in-band mechanism would be to send a
> NOTIFY to the parental agent. I can only find a little discussion of this
> idea in 2014, and it wasn't very enthusiastic - there were questions like,
> how do you k
10 matches
Mail list logo
