Re: login.authorize.net has A and CNAME records

Mark Andrews writes: > It shouldn’t matter. Only non-rfc-compliant servers allow A and CNAME > to co-exist at the same name. That combination was prohibited by RFC > 1034. Right. Thanks. I confused myself multiple times here ;-) The issue seems to be that the cloudflare servers takes a

Re: login.authorize.net has A and CNAME records

> On 7 Apr 2021, at 17:20, Bjørn Mork wrote: > > Bjørn Mork writes: > >> Seth Mattinen writes: >>> On 4/6/21 11:35 AM, Arne Jensen wrote: login.authorize.net. is a CNAME, but does not have any A records itself. >>> >>> >>> This one returns A records: >> >> Looks like they host DNS

Re: login.authorize.net has A and CNAME records

Bjørn Mork writes: > Seth Mattinen writes: >> On 4/6/21 11:35 AM, Arne Jensen wrote: >>> login.authorize.net. is a CNAME, but does not have any A records itself. >> >> >> This one returns A records: > > Looks like they host DNS on both cloudflare and akami, but zone contents > are different on

Re: login.authorize.net has A and CNAME records

Seth Mattinen writes: > On 4/6/21 11:35 AM, Arne Jensen wrote: >> login.authorize.net. is a CNAME, but does not have any A records itself. > > > This one returns A records: Looks like they host DNS on both cloudflare and akami, but zone contents are different on the two platforms:

Re: login.authorize.net has A and CNAME records

For the thread -- we're aware and looking into this. n...@cloudflare.com being the best place to report these kinds of things. __ *Justin Paine* He/Him/His Head of Trust & Safety 101 Townsend St, San Francisco, CA 94107

Re: login.authorize.net has A and CNAME records

> On 7 Apr 2021, at 05:59, Arne Jensen wrote: > > > Den 06-04-2021 kl. 21:47 skrev Seth Mattinen: >> >>> >>> What kind of local problem or network problems could cause a servfail >>> response from the authoritative ns? >> >> >> >> I'm beginning to think this is a DNSSEC related problem,

Re: login.authorize.net has A and CNAME records

Den 06-04-2021 kl. 21:47 skrev Seth Mattinen: > >> >> What kind of local problem or network problems could cause a servfail >> response from the authoritative ns? > > > > I'm beginning to think this is a DNSSEC related problem, I'll ask on > the pdns-users list. I see it's asking for a DS record

Re: login.authorize.net has A and CNAME records

Seth Mattinen wrote: > > I'm beginning to think this is a DNSSEC related problem, I'll ask on the > pdns-users list. I see it's asking for a DS record on > login.authorize.net.cdn.cloudflare.net when the nearest one appears to be at > cloudflare.net, so for some reason that's not being applied

Re: login.authorize.net has A and CNAME records

What kind of local problem or network problems could cause a servfail response from the authoritative ns? I'm beginning to think this is a DNSSEC related problem, I'll ask on the pdns-users list. I see it's asking for a DS record on login.authorize.net.cdn.cloudflare.net when the

Re: login.authorize.net has A and CNAME records

On 4/6/21 11:35 AM, Arne Jensen wrote: login.authorize.net. is a CNAME, but does not have any A records itself. This one returns A records: ; <<>> DiG 9.10.3-P4-Debian <<>> A login.authorize.net @ns0210.secondary.cloudflare.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<-

Re: login.authorize.net has A and CNAME records

On 4/6/21 11:35 AM, Arne Jensen wrote: Den 06-04-2021 kl. 19:50 skrev Seth Mattinen: On 4/6/21 9:33 AM, Seth Mattinen wrote: Is anyone from authorize.net on here? You are publishing both an A and CNAME record for login.authorize.net, and the CNAME points to

Re: login.authorize.net has A and CNAME records

Den 06-04-2021 kl. 19:50 skrev Seth Mattinen: > On 4/6/21 9:33 AM, Seth Mattinen wrote: >> Is anyone from authorize.net on here? You are publishing both an A >> and CNAME record for login.authorize.net, and the CNAME points to >> login.authorize.net.cdn.cloudflare.net which doesn't resolve. > >

Re: login.authorize.net has A and CNAME records

On 4/6/21 9:33 AM, Seth Mattinen wrote: Is anyone from authorize.net on here? You are publishing both an A and CNAME record for login.authorize.net, and the CNAME points to login.authorize.net.cdn.cloudflare.net which doesn't resolve. Looks like this may be a cloudflare related issue; I'm