We haven't been having any problems for years. This BAD_ADDRESS problem just started out of the blue a few months ago and we hadn't made any changes back then. Recently we upgraded our Domain Controllers to SP-2 (we thought it might fix this issue but it didn't).
I had DHCP logging on. Here is a clip of the logs that record the error. Anyone able to decipher what's happening?
30,04/21/09,01:14:15,DNS Update Request,91.3.168.192,NMS727.NMSLAB.local,,
13,04/21/09,01:14:15,Conflict,192.168.3.91,BAD_ADDRESS,,
32,04/21/09,01:14:15,DNS Update Successful,192.168.3.91,NMS727.NMSLAB.local,,
30,04/21/09,01:14:25,DNS Update Request,91.3.168.192,BAD_ADDRESS,,
15,04/21/09,01:14:25,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
32,04/21/09,01:14:25,DNS Update Successful,192.168.3.91,BAD_ADDRESS,,
15,04/21/09,01:14:26,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:27,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:28,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:29,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:30,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:31,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:32,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:33,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:34,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:35,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:36,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:37,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:38,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:39,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:40,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:41,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,
15,04/21/09,01:14:42,NACK,192.168.3.91,NMS727.NMSLAB.local,0010C6A247F8,