I use Cloudflare’s DNS, i.e. 1.1.1.1 and 1.0.0.1.
Since today I have issues connecting to https://www.rei.com.
Checking with dig it seems that 1.1.1.1 returns a different IP than for example the competitors:
dig @1.1.1.1 www.rei.com A
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @1.1.1.1 www.rei.com A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58149
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;www.rei.com. IN A
;; ANSWER SECTION:
www.rei.com. 1072 IN CNAME www.rei.com.edgekey.net.
www.rei.com.edgekey.net. 5 IN CNAME e739.a.akamaiedge.net.
e739.a.akamaiedge.net. 20 IN A 104.87.142.13
;; Query time: 14 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Dec 28 14:56:21 PST 2019
;; MSG SIZE rcvd: 125
Versus your competitor:
dig @8.8.8.8 www.rei.com A
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @8.8.8.8 www.rei.com A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18909
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.rei.com. IN A
;; ANSWER SECTION:
www.rei.com. 3496 IN CNAME www.rei.com.edgekey.net.
www.rei.com.edgekey.net. 110 IN CNAME e739.a.akamaiedge.net.
e739.a.akamaiedge.net. 8 IN A 23.7.135.149
;; Query time: 13 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Dec 28 14:56:07 PST 2019
;; MSG SIZE rcvd: 125
Connecting to the website with Cloudflare’s DNS gives issues.
/usr/local/bin/wget --delete-after --dns-servers=1.1.1.1 --tries=1 http://rei.com
--2019-12-28 14:39:19-- http://rei.com/
Resolving rei.com (rei.com)... 69.192.138.229
Connecting to rei.com (rei.com)|69.192.138.229|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.rei.com/ [following]
--2019-12-28 14:39:19-- https://www.rei.com/
Resolving www.rei.com (www.rei.com)... 104.87.142.13
Connecting to www.rei.com (www.rei.com)|104.87.142.13|:443... failed: Connection timed out.
Giving up.
With the competitor:
/usr/local/bin/wget --delete-after --dns-servers=8.8.8.8 --tries=1 http://rei.com
--2019-12-28 15:51:16-- http://rei.com/
Resolving rei.com (rei.com)... 23.196.195.206
Connecting to rei.com (rei.com)|23.196.195.206|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.rei.com/ [following]
--2019-12-28 15:51:16-- https://www.rei.com/
Resolving www.rei.com (www.rei.com)... 104.70.204.186
Connecting to www.rei.com (www.rei.com)|104.70.204.186|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html.tmp’
index.html.tmp [ <=> ] 236.69K --.-KB/s in 0.05s
2019-12-28 15:51:16 (4.61 MB/s) - ‘index.html.tmp’ saved [242374]
Removing index.html.tmp.
Not sure if it’s a TTL issue, or a wrong configuration.
Same issues for: