Resolution Failure on macys.com when using 1.1.1.1 DNS

I was trying to visit macys.com today and the site seemed to be loading slowly and it ultimately ended up loading as follows:

As you can see in the console, the site is unable to load properly due to name resolution failures.

I tried this on my Mac and my PC (both running 1.1.1.1), and the issue occurs on both. Changing my IPv4 and IPv6 DNS servers back to automatic (removing 1.1.1.1) resolved these issues.

Diagnostic output from console:

Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…05e04c597ec49.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…353ab6389be51.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…53f889e79cff5.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…c063da7ccf5f4.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…623dd1b47da92.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…f68f862bed254.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
home-page.vendor.com…23e26193e38b04.js:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
home-page.core.vendo…bc73827effb3ff.js:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
home-page.mcom.adf5c3b….js:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…fb2eb820811f8.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
assets.macysassets.c…5b4c593a6179d.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
VisitorAPI.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
vendors~dynamic-slid…0cb0d6a3d15f8.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED
vendors~prosFactory.…dd3e0f77640ad.css:1 Failed to load resource: net::ERR_NAME_RESOLUTION_FAILED

Diagnostics link: 1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver

PS C:\Users\Jad Chaar> nslookup example.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34

PS C:\Users\Jad Chaar> nslookup example.com 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Non-authoritative answer:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34

PS C:\Users\Jad Chaar> nslookup example.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    example.com
Addresses:  2606:2800:220:1:248:1893:25c8:1946
          93.184.216.34

PS C:\Users\Jad Chaar> nslookup -class=chaos -type=txt id.server 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
id.server       text =

        "DTW"
PS C:\Users\Jad Chaar> nslookup -class=chaos -type=txt id.server 1.0.0.1
Server:  one.one.one.one
Address:  1.0.0.1

Non-authoritative answer:
id.server       text =

        "DTW"

If DNSViz is correct, all but one of macysassets.com’s nameservers are returning SERVFAIL errors. (And the good one doesn’t respond to TCP!)

http://dnsviz.net/d/macysassets.com/dnssec/

Using Quad9, I can resolve the subdomains, but not quickly or reliably.

1 Like

I just tried accessing macys.com on my PC again and the issue seems to be resolved (huh puns!). It must have been a temporary issue.