tags 605808 + fixed-upstream thanks > According to RFC 5006, section 5.1, the lifetime field of an RDNSS > option has a special meaning for the values of zero and all-ones: > > A value of all one bits (0xffffffff) represents infinity. A value > of zero means that the RDNSS address MUST no longer be used. > > Thus said, rdnssd unconditionally adds the value of lifetime to the > current timestamp (now), which causes two undesired effects: > > 1. In the case of all ones, it causes the unsigned 32-bit expiry > variable to wrap-around and the subsequent code to completely ignore > the DNS servers specified.
This is fixed, thanks. > 2. In the case of lifetime being zero, it ignores the current RDNSS, > but does not remove the specified nameservers from the server list. I am unable to reproduce the issue. The lifetime of the server matching that RDNSS option is updated to zero, and it is later deleted after sorting and checking the list for expired entries. -- Pierre Ynard -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
