Re: 2038 problem and BIND.

2010-09-20 Thread Tony Finch
On Mon, 20 Sep 2010, Alan Clegg wrote: > > All signature expire times are in MMDDHHMMSS format in the zone data > and are handled correctly as far as BIND deals with it. > > If your OS deals with the 2038 issue correctly, then BIND will as well. RFC 4034 says that the signature validity times

Re: 2038 problem and BIND.

2010-09-20 Thread Alan Clegg
On 9/19/2010 6:57 AM, kalpesh varyani wrote: > > > I would just like to know, how BIND takes care of the 2038 problem. > Since now DNSSEC has a lot to do with timings, there could be issues if > someone would set the signature expiry time to a large value (possibly > after Y2K38). This can create

2038 problem and BIND.

2010-09-19 Thread kalpesh varyani
Hi Experts, I would just like to know, how BIND takes care of the 2038 problem. Since now DNSSEC has a lot to do with timings, there could be issues if someone would set the signature expiry time to a large value (possibly after Y2K38). This can create problems, if care is not taken in BIND code.