Epic Games' CDN failing to resolve; Google's DNS works

I’m on a Linux desktop using 1.1.1.1 as my DNS resolver, but right now some Epic Game’s CDNs are failing to resolve (this one is used to download the Epic Games launcher):

$ nslookup launcher-public-service-prod06.ol.epicgames.com 1.1.1.1
;; connection timed out; no servers could be reached

Another domain (used to host static files such as javascript, CSS, images for the Epic Games Store):

$ nslookup media-cdn.epicgames.com 1.1.1.1
;; connection timed out; no servers could be reached

Now using Google’s DNS:

$ nslookup launcher-public-service-prod06.ol.epicgames.com 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
launcher-public-service-prod06.ol.epicgames.com	canonical name = acc-launcher-public-service-prod06.ol.epicgames.com.
acc-launcher-public-service-prod06.ol.epicgames.com	canonical name = d2vryputvprrok.cloudfront.net.
Name:	d2vryputvprrok.cloudfront.net
Address: 65.8.205.75
Name:	d2vryputvprrok.cloudfront.net
Address: 65.8.205.98
Name:	d2vryputvprrok.cloudfront.net
Address: 65.8.205.87
Name:	d2vryputvprrok.cloudfront.net
Address: 65.8.205.76

And finally:

$ nslookup media-cdn.epicgames.com 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
media-cdn.epicgames.com	canonical name = d1dxcvubdbe4ji.cloudfront.net.
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 65.8.205.105
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 65.8.205.58
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 65.8.205.53
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 65.8.205.115

Is this still happening for you? For me it works

Server: one.one.one.one
Address: 1.1.1.1

Nicht autorisierende Antwort:
Name: d2vryputvprrok.cloudfront.net
Addresses: 13.249.13.85
13.249.13.81
13.249.13.23
13.249.13.84
Aliases: launcher-public-service-prod06.ol.epicgames.com
acc-launcher-public-service-prod06.ol.epicgames.com

Server: one.one.one.one
Address: 1.1.1.1

Nicht autorisierende Antwort:
Name: d1dxcvubdbe4ji.cloudfront.net
Addresses: 99.86.91.106
99.86.91.58
99.86.91.84
99.86.91.13
Aliases: media-cdn.epicgames.com

@ oneandonlyjason Yep, Cloudflare’s still not resolving for me. Google works still.

Ok thats really strange… For me its working so it should work for everyone i guess. Since when is this happening?

It’s been happening for months. I mean, sometimes it does resolve. I noticed that when Epic Games is giving away free games (like right now), the problem occurs.

Could it be related to routing? I assume we’re from different countries (I’m from Brazil), so I don’t think it’s that unusual that works for you but not for me.

Yeah, I just used a US VPN and now I can resolve just fine:

$ nslookup media-cdn.epicgames.com 1.1.1.1
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
media-cdn.epicgames.com	canonical name = d1dxcvubdbe4ji.cloudfront.net.
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 13.32.87.71
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 13.32.87.84
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 13.32.87.61
Name:	d1dxcvubdbe4ji.cloudfront.net
Address: 13.32.87.125

I believe this indicates there are some issues with Cloudflare’s South America servers…

That could be a case. Then Cloudflare would need to take a look into this. When you have a Domain with Cloudflare you can open a Support Ticket with them in your Account.

Hi @ppchwcmwjzlvqipfxg, sorry about the issues, it seems like some traffic ended up ratelimited. Can you check if it’s working okay for you now?

2 Likes

I’m so sorry for the late response.

I just tried to resolve media-cdn.epicgames.com again:

$ nslookup media-cdn.epicgames.com 1.1.1.1
;; connection timed out; no servers could be reached

FWIW, my ISP is called NET Virtua and running the tracepath command against 1.1.1.1 gives me this:

$ tracepath 1.1.1.1
 1?: [LOCALHOST]                      pmtu 1500
 1:  _gateway                                              2.596ms 
 1:  _gateway                                              1.772ms 
 2:  no reply
 3:  bd0501c9.virtua.com.br                               18.069ms 
 4:  one.one.one.one                                      27.239ms reached
     Resume: pmtu 1500 hops 4 back 4

So far, I’ve only had issues with Epic’s domains, at least as far as I remember.

Hm, I don’t see any failures for that name. Can you capture some debug information as per Have problems with 1.1.1.1? *Read Me First* ?

Thanks for the link! Here are my results:

1st:

$ dig media-cdn.epicgames.com @1.1.1.1

; <<>> DiG 9.16.13 <<>> media-cdn.epicgames.com @1.1.1.1
;; global options: +cmd
;; connection timed out; no servers could be reached

2nd:

$ dig media-cdn.epicgames.com @1.0.0.1

; <<>> DiG 9.16.13 <<>> media-cdn.epicgames.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2315
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;media-cdn.epicgames.com.	IN	A

;; ANSWER SECTION:
media-cdn.epicgames.com. 262	IN	CNAME	d1dxcvubdbe4ji.cloudfront.net.
d1dxcvubdbe4ji.cloudfront.net. 22 IN	A	65.8.205.53
d1dxcvubdbe4ji.cloudfront.net. 22 IN	A	65.8.205.115
d1dxcvubdbe4ji.cloudfront.net. 22 IN	A	65.8.205.58
d1dxcvubdbe4ji.cloudfront.net. 22 IN	A	65.8.205.105

;; Query time: 19 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: ter mar 30 01:19:53 -03 2021
;; MSG SIZE  rcvd: 159

3rd:

$ dig media-cdn.epicgames.com @8.8.8.8

; <<>> DiG 9.16.13 <<>> media-cdn.epicgames.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1376
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;media-cdn.epicgames.com.	IN	A

;; ANSWER SECTION:
media-cdn.epicgames.com. 299	IN	CNAME	d1dxcvubdbe4ji.cloudfront.net.
d1dxcvubdbe4ji.cloudfront.net. 59 IN	A	65.8.205.115
d1dxcvubdbe4ji.cloudfront.net. 59 IN	A	65.8.205.58
d1dxcvubdbe4ji.cloudfront.net. 59 IN	A	65.8.205.53
d1dxcvubdbe4ji.cloudfront.net. 59 IN	A	65.8.205.105

;; Query time: 23 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: ter mar 30 01:21:15 -03 2021
;; MSG SIZE  rcvd: 159

4th:

$ dig +short CHAOS TXT id.server @1.1.1.1
;; connection timed out; no servers could be reached

5th:

$ dig +short CHAOS TXT id.server @1.0.0.1
"GRU"

6th:

$ nslookup -type=txt whoami.Cloudflare.com ns3.Cloudflare.com
Server:		ns3.Cloudflare.com
Address:	2400:cb00:2049:1::a29f:21#53

whoami.Cloudflare.com	text = "2804:14d:9083:8537:20a2:7b5f:xxxx:xxxx"

It seems like your ISP is using 1.1.1.1 address internally. It should resolve okay for you if you use 1.0.0.1 or any of the alternative addresses 1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver

1 Like