1.1.1.1 timeout resolving opennet.salliemae.com

We use 1.1.1.1 and 1.0.0.1 as a reverse DNS and we get a timeout response trying to resolve opennet.salliemae.com.

It works using the google DNS servers

Thank You
Andrea

opennet.salliemae.com appears to be a CNAME for 7l67vyr.x.incapdns.net.

The latter resolves fine through Cloudflare, so the issue probably really is with the salliemae.com host.

http://dnsviz.net/d/opennet.salliemae.com/dnssec/ looks okay, but it seems as if the domain itself might have some DNSSEC issues
http://dnsviz.net/d/salliemae.com/dnssec/

If this is your domain, try to address these issues and check whether it fixes the resolution. Otherwise drop Cloudflare’s support an email at their [email protected] address. Maybe it is something they can fix, if not the domain owner will have to.

Seems like it’s fixed.

dig @1.1.1.1 opennet.salliemae.com

; <<>> DiG 9.10.6 <<>> @1.1.1.1 opennet.salliemae.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50319
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;opennet.salliemae.com. IN A

;; ANSWER SECTION:
opennet.salliemae.com. 600 IN CNAME 7l67vyr.x.incapdns.net.
7l67vyr.x.incapdns.net. 30 IN A 45.60.122.53

;; Query time: 189 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Oct 09 21:58:43 CDT 2019
;; MSG SIZE rcvd: 102

dig @1.0.0.1 opennet.salliemae.com

; <<>> DiG 9.10.6 <<>> @1.0.0.1 opennet.salliemae.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31026
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;opennet.salliemae.com. IN A

;; ANSWER SECTION:
opennet.salliemae.com. 591 IN CNAME 7l67vyr.x.incapdns.net.
7l67vyr.x.incapdns.net. 21 IN A 45.60.122.53

;; Query time: 127 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Wed Oct 09 21:58:52 CDT 2019
;; MSG SIZE rcvd: 102

1 Like

It appears the domain’s configuration issues have been (partially at least) fixed and it does seem as if Cloudflare could resolve it now, though I still run into timeouts. I guess PoP related.

Hello everyone, thank you for your support, now it seems it is working regularly.

The strange thing was that we get the error only using the cloudflare DNS as our forwarders, while trying with google DNS we can resolve the site immediatly.

Thank you
Andrea