From Qwest/CL:
"we are aware of the issue and expect this to be resolved next month."
>
> Yes please.
>
>> On 13 Sep 2018, at 2:45 am, Anne P. Mitchell, Esq.
>> wrote:
>>
>>
>> Would you like us to send this to our Qwest/CenturyLink contact?
>>
>> Anne P. Mitchell,
>> Attorney at Law
>>
Yes please.
> On 13 Sep 2018, at 2:45 am, Anne P. Mitchell, Esq.
> wrote:
>
>
> Would you like us to send this to our Qwest/CenturyLink contact?
>
> Anne P. Mitchell,
> Attorney at Law
> GDPR, CCPA (CA) & CCDPA (CO) Compliance Consultant
> Author: Section 6 of the CAN-SPAM Act of 2003 (the F
Would you like us to send this to our Qwest/CenturyLink contact?
Anne P. Mitchell,
Attorney at Law
GDPR, CCPA (CA) & CCDPA (CO) Compliance Consultant
Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law)
Legislative Consultant
CEO/President, Institute for Social Internet Pub
I know it takes some time to upgrade DNS servers to ones that are actually
protocol compliant but 4+ years is ridiculous. Your servers are the only
ones serving the Alexa top 1M sites or the GOV zone that still return BADVERS
to EDNS queries with a EDNS option present. This was behaviour made up
On Thu, Jun 07, 2018 at 11:31:15AM -0400,
harbor235 wrote
a message of 5 lines which said:
> I was hoping for some DNS wisdom,
Then this is more a dns-operations mailing list issue.
> would a change in a SOA record cause a
> DNSSEC broken trust chain? incorrect RRSIG?
No. The SOA record is
I was hoping for some DNS wisdom, would a change in a SOA record cause a
DNSSEC broken trust chain? incorrect RRSIG?
Mike
6 matches
Mail list logo