Google DNS resolver fails for wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws

[jonathan...@gmail.com]

Hi,

I have been having issues with uploading files to WeTransfer since yesterday from France using 8.8.8.8/8.8.4.4. Works with my ISP's DNS resolver. Same behaviour can be observed on different machines (laptops, smartphones).

Following the troubleshooting guide at https://developers.google.com/speed/public-dns/docs/troubleshooting :

Step 1: looks OK, can't really tell...

- https://intodns.com/s3.eu-west-1.amazonaws.com

- http://dnsviz.net/d/wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws/dnssec/

Step 2: looks OK, ends with:

13  8.8.8.8  23.758 ms  19.020 ms

Step 3: this is getting interesting:

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8

;; global options: +cmd

;; connection timed out; no servers could be reached

Step 4: same result

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8 +cd

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8 +cd

;; global options: +cmd

;; connection timed out; no servers could be reached

Step 5: works fine with other open resolvers:

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @4.2.2.1

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @4.2.2.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9828

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. IN A

;; ANSWER SECTION:

wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. 1 IN CNAME s3.eu-west-1.amazonaws.com.

s3.eu-west-1.amazonaws.com. 1 IN A 52.218.104.154

;; Query time: 37 msec

;; SERVER: 4.2.2.1#53(4.2.2.1)

;; WHEN: Sat Oct 20 20:04:41 CEST 2018

;; MSG SIZE  rcvd: 102

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @4.2.2.2

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @4.2.2.2

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46915

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. IN A

;; ANSWER SECTION:

wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. 1 IN CNAME s3.eu-west-1.amazonaws.com.

s3.eu-west-1.amazonaws.com. 1 IN A 52.218.48.36

;; Query time: 28 msec

;; SERVER: 4.2.2.2#53(4.2.2.2)

;; WHEN: Sat Oct 20 20:04:45 CEST 2018

;; MSG SIZE  rcvd: 102

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @208.67.222.222

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @208.67.222.222

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44582

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. IN A

;; ANSWER SECTION:

wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. 37 IN CNAME s3.eu-west-1.amazonaws.com.

s3.eu-west-1.amazonaws.com. 5 IN A 52.218.48.60

;; Query time: 23 msec

;; SERVER: 208.67.222.222#53(208.67.222.222)

;; WHEN: Sat Oct 20 20:04:55 CEST 2018

;; MSG SIZE  rcvd: 113

$ dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @208.67.220.220

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @208.67.220.220

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17413

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. IN A

;; ANSWER SECTION:

wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. 300 IN CNAME s3.eu-west-1.amazonaws.com.

s3.eu-west-1.amazonaws.com. 5 IN A 52.218.64.236

;; Query time: 35 msec

;; SERVER: 208.67.220.220#53(208.67.220.220)

;; WHEN: Sat Oct 20 20:05:01 CEST 2018

;; MSG SIZE  rcvd: 113

Best regards,

Jonathan

[atg...@gmail.com]

Hi,

I confirm this problem

It's only localized on the cache hosted in Interxion MRS1 (Marseille)

It's doesn't occure on the cache of Paris.

Arnaud

[whatthe...@gmail.com]

Hi,

I can also confirm this problem from France.

I exposed another issue which may be linked to this one by a way or another : https://groups.google.com/forum/#!topic/public-dns-discuss/ayeduiMySII

Le lundi 22 octobre 2018 14:46:37 UTC+2, Jonathan Derrough a écrit :

[whatthe...@gmail.com]

It seems that this problem was also solved by itself.

[Jonathan Derrough]

Confirmed, thanks for the heads up.

[andrzej....@gmail.com]

andrzejs-MacBook-Air-3:~ andrzej$  dig wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8

; <<>> DiG 9.10.6 <<>> wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48063

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. IN A

;; ANSWER SECTION:

wetransfer-eu-prod-outgoing.s3.eu-west-1.amazonaws.com. 299 IN CNAME s3.eu-west-1.amazonaws.com.

s3.eu-west-1.amazonaws.com. 4 IN A 54.231.134.51

;; Query time: 47 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)