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
login.authorize.net.cdn.cloudflare.net which doesn't resolve.
Looks like this may be a cloudflare related issue; I'm just getting
servfail responses across the board to my on-net resolvers from
cloudflare (not using public dns services).
Sounds more like a local problem on your end, or issues between you and
the CloudFlare facility you're being routed to.
We peer with cloudflare in LAX so the connection is relatively direct.
Example trace:
2021-04-06T10:40:52.859117-07:00 dnscache1 pdns_recursor[522]:
Nameserver ns2.cloudflare.net IPs: 2400:cb00:2049:1::c629:de83(3.70ms),
198.41.222.131(8.02ms)
2021-04-06T10:40:52.859410-07:00 dnscache1 pdns_recursor[522]:
login.authorize.net.cdn.cloudflare.net: Resolved 'cloudflare.net' NS
ns2.cloudflare.net to: 2400:cb00:2049:1::c629:de83, 198.41.222.131
2021-04-06T10:40:52.859720-07:00 dnscache1 pdns_recursor[522]:
login.authorize.net.cdn.cloudflare.net: Trying IP
[2400:cb00:2049:1::c629:de83]:53, asking
'login.authorize.net.cdn.cloudflare.net|DS'
2021-04-06T10:40:52.860013-07:00 dnscache1 pdns_recursor[522]:
login.authorize.net.cdn.cloudflare.net: ns2.cloudflare.net
(2400:cb00:2049:1::c629:de83) returned a ServFail, trying sibling IP or NS
2021-04-06T10:40:52.860324-07:00 dnscache1 pdns_recursor[522]:
login.authorize.net.cdn.cloudflare.net: Trying IP 198.41.222.131:53,
asking 'login.authorize.net.cdn.cloudflare.net|DS'
2021-04-06T10:40:52.860628-07:00 dnscache1 pdns_recursor[522]:
login.authorize.net.cdn.cloudflare.net: ns2.cloudflare.net
(198.41.222.131) returned a ServFail, trying sibling IP or NS
What kind of local problem or network problems could cause a servfail
response from the authoritative ns?
