SERVFAIL resolving slimages.macysassets.com using 1.1.1.1, 1.0.0.1, dig, cloudflared

bug

#1

Other domains work, this one doesn’t.

$ dig slimages.macysassets.com @1.0.0.1

; <<>> DiG 9.10.6 <<>> slimages.macysassets.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57673
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 4219 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Wed Nov 14 17:57:52 PST 2018
;; MSG SIZE  rcvd: 53

$ dig slimages.macysassets.com @1.1.1.1

; <<>> DiG 9.10.6 <<>> slimages.macysassets.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13059
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 4220 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Nov 14 17:57:58 PST 2018
;; MSG SIZE  rcvd: 53

$ dig slimages.macysassets.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> slimages.macysassets.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54048
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;slimages.macysassets.com.	IN	A

;; ANSWER SECTION:
slimages.macysassets.com. 2799	IN	CNAME	slimages.macysassets.com.edgekey.net.
slimages.macysassets.com.edgekey.net. 189 IN CNAME e5791.a.akamaiedge.net.
e5791.a.akamaiedge.net.	19	IN	A	23.197.97.33

;; Query time: 56 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Nov 14 17:58:01 PST 2018
;; MSG SIZE  rcvd: 152

Error: cloudflare/cloudflare/cloudflared 2018.10.5 already installed

$ cat /usr/local/etc/cloudflared/config.yml 
proxy-dns: true
proxy-dns-upstream:
 - https://1.1.1.1/dns-query
 - https://1.0.0.1/dns-query

#2

This issue is occurring again today, and as before, 8.8.8.8 can resolve it while 1.1.1.1 cannot. The forum prohibits me from posting either the dig output or the cloudflare-dns.com help link associated with today’s event, but the details are unchanged from previously.