RE: Strange DNSsec failure [was incorrectly sent Thursday night]

I'm wondering if it's been fixed ... I flushed the DNS cache on the problem servers again later this morning and now it's staying good, even after TTL. We'll see if it stays that way. Thanks, Frank -Original Message- From: bind-users On Behalf Of Mark Elkins Sent: Saturday, April 13

Re: Strange DNSsec failure [was incorrectly sent Thursday night]

Works fine for me? - unless its been fixed in  the meantime. This is stock standard bind. Nothing funny at all on both the query machine and the DNSSEC aware resolver. Both run the same version of BIND. $ dig  mx1.comcast.net ; <<>> DiG 9.12.3-P4 <<>> mx1.comcast.net ;; global options: +cm