No A record for lightsail.aws.amazon.com

A few times now I have had to run a purge against lightsail.aws.amazon.com in order for Cloudflare to return an A record. As soon as I run the purge, an A record is returned. Below is a copy of my dig before and after I run the purge.

dig lightsail.aws.amazon.com
; <<>> DiG 9.10.6 <<>> lightsail.aws.amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9489
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
; PAD: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (".......................................................................")

;; QUESTION SECTION:

;lightsail.aws.amazon.com. IN A
;; Query time: 63 msec
;; SERVER: x
;; WHEN: Mon May 20 11:20:48 BST 2019
;; MSG SIZE rcvd: 128

dig lightsail.aws.amazon.com

; <<>> DiG 9.10.6 <<>> lightsail.aws.amazon.com
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12598
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
; PAD: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ("................................")

;; QUESTION SECTION:

;lightsail.aws.amazon.com. IN A

;; ANSWER SECTION:

lightsail.aws.amazon.com. 60 IN CNAME lbr.lightsail-lbr.com.
lbr.lightsail-lbr.com. 60 IN CNAME eu-west-3.lightsail.aws.amazon.com.
eu-west-3.lightsail.aws.amazon.com. 60 IN CNAME eu-west-3.console.aws.amazon.com.
eu-west-3.console.aws.amazon.com. 60 IN CNAME console.eu-west-3.amazonaws.com.
console.eu-west-3.amazonaws.com. 60 IN A 52.46.68.59

;; Query time: 103 msec
;; SERVER: x
;; WHEN: Mon May 20 11:21:44 BST 2019
;; MSG SIZE rcvd: 421

So I can dig it just fine at 1.1.1.1

dig lightsail.aws.amazon.com @1.1.1.1

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> lightsail.aws.amazon.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63560
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;lightsail.aws.amazon.com.      IN      A

;; ANSWER SECTION:
lightsail.aws.amazon.com. 60    IN      CNAME   lbr.lightsail-lbr.com.
lbr.lightsail-lbr.com.  60      IN      CNAME   ca-central-1.lightsail.aws.amazon.com.
ca-central-1.lightsail.aws.amazon.com. 60 IN CNAME ca-central-1.console.aws.amazon.com.
ca-central-1.console.aws.amazon.com. 49 IN CNAME console.ca-central-1.amazonaws.com.
console.ca-central-1.amazonaws.com. 49 IN A     52.94.104.110

;; Query time: 526 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon May 20 11:34:19 DST 2019
;; MSG SIZE  rcvd: 229

To me, it appears to be a more network issue because you do not get an answer with the first dig.