Maintained by: NLnet Labs

[Unbound-users] NOTIFY implementation to unbound

Greg A. Woods
Mon Oct 19 19:16:53 CEST 2009


At Wed, 14 Oct 2009 11:48:43 -0700 (PDT), Aaron Hopkins <lists at die.net> wrote:
Subject: Re: [Unbound-users] NOTIFY implementation to unbound
> 
> However, without the ability to check SOA serial numbers on everything in
> the cache, there's a race condition with using NOTIFY like this.

No, not really -- there's no race condition possible.

A nameserver must only send NOTIFY to other interested servers _after_
it has updated its local copy of the zone.

Any new queries received after the zone has been updated will therefore
be answered from the up-to-date records, just as you would expect.

A caching server such as Unbound receiving a NOTIFY for a zone need only
flush all records matching that zone and then continue on as normal.

-- 
						Greg A. Woods

+1 416 218-0098                VE3TCP          RoboHack <woods at robohack.ca>
Planix, Inc. <woods at planix.com>      Secrets of the Weird <woods at weird.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20091019/17b6bc36/attachment.pgp>