[bind10-dev] Datasource discussion
zhanglikun
zlkzhy at gmail.com
Thu Jan 14 14:23:10 UTC 2010
Shane
> The "fuzziness" I'm talking about is on query results, so for example:
>
> 1. Admin does a DDNS update to update an NS RRSET: modify the NS
> RRSET to add a new name server, then add an A record for it.
> (All in theory atomic since this is DDNS.)
> 2. User queries for this NS RRSET, and gets the updated NS RRSET,
> but the A record is not yet there, so it is not added to the
> additional section. This may result in an extra query
> (hopefully), or a confused user.
>
> I think this isn't that bad. It should at least be written down. :)
Maybe it's a bad news for rrsets with RRSIG. If one NS RRSET has two
records:
com NS a.com
com NS b.com
com RRSIG NS ...
1. Admin does a DDNS update to add/delete a record to NS RRSET, but the
RRSIG hasn't been updated, user will get the new NS RRSET with its old
RRSIG,
2. The recursor will treat the answer as invalid, it will cause some
problem.
Zhanglikun
More information about the bind10-dev
mailing list