On 6/20/19 7:16 AM, Remi Gacogne wrote:
> On 6/20/19 4:01 PM, Mike wrote:
>> I think you got it - the AA bit isn't set, so they are going to be
>> failing lots of places. I noticed however that googledns didn't seem to
>> have a problem with it. Wondering if this 'relaxed functionality' is
>> just
On Thu, Jun 20, 2019 at 07:01:24AM -0700, Mike wrote:
> On 6/19/19 11:45 PM, Otto Moerbeek wrote:
> > Please always specify version and platform you are running.
> >
> > That said, both https://dnssec-analyzer.verisignlabs.com/efax.com and
> > https://dnssec-analyzer.verisignlabs.com/ report DNSSE
On 6/20/19 4:01 PM, Mike wrote:
> I think you got it - the AA bit isn't set, so they are going to be
> failing lots of places. I noticed however that googledns didn't seem to
> have a problem with it. Wondering if this 'relaxed functionality' is
> just suicidal on google's part or perhaps a future
On 6/19/19 11:45 PM, Otto Moerbeek wrote:
> Please always specify version and platform you are running.
>
> That said, both https://dnssec-analyzer.verisignlabs.com/efax.com and
> https://dnssec-analyzer.verisignlabs.com/ report DNSSEc problems with
> this domain.
>
Ugh, my bad for failing to pos
Hi Mike,
On 6/20/19 7:20 AM, Mike wrote:
> I noticed tonight that resolving for 'efax.com' is failing and my
> resolvers (pdns_recursor) are returning 'servfail' while google dns is
> returing the data.
>
>
> The specfic error I notice seems to be:
>
> Removing record 'inbound.efax.
