Thanks for checking.
Well, then I can suggest using Cloudflare WARP or ZeroTrust one more time.
Using a VPN is fine as a temporary fix, but I would ultimately like to see AT&T remediate whatever it is on their network that is causing this. Hence, my advocating for customers affected by this to contact their ISPs directly.
As a workaround for whatever is wrong with ISP or DNS, anyone try B2 via S3?
Old enough buckets can’t do it (I think I used rclone move to move server-side).
Locate an S3 Endpoint URL shows how to find the S3 URL. Native are different.
Doesn’t give first appearance of DNS blocking by giving a bad address. Odd.
Points out that if one doesn’t like ISP DNS, others exist. Just more ideas to try.
If the ISP uses some sort of blocker all in their network, the S3 trick might help.
From what I see above - Backblaze B2 Stopped working recently - #20 by amloessb - there is no DNS blocking, the destination is blocked by its IP address.
Fortunately, s3endpoint resolves into multiple other IPs. Good idea.
I’m not going to convince anyone, just want to share this if anybody will ever need to go that path.
In order to use Cloudflare WARP there is no need in installing their client software, there is also no need in redirecting all the traffic through them.
What is required on the client side (PC, server, router) is a standard WireGuard client.
Googling for something like “warp config generator“ should help with the configuration.
Once configuration file is obtained there is no need to use “DNS=” or redirect the existing default gateway, it will be sufficient to list only specific [B2] IPs or subnets in “AllowedIPs=“ statement.
I can confirm I have the exact issue. I’m going to get a ticket going with ATT support for this issue. This should not be happening…
This isn’t DNS, it’s routing or a firewall issue.
Or it’s whatever the ISP is doing to block. For some other people, it was DNS.
That’s probably the only way to fix it, unless you want to try the S3 route instead.
EDIT 1:
Citation on DNS from 2021 which was at a registrar level:
Recent Outages: Why We Accelerated Registry Changes
Citation on DNS from 3 days ago:
This talks about a blocklist. Maybe once on one, there are many ways to block?
If it was DNS, I’d get an NXDOMAIN or something similar in the response or EDNS error codes. I can resolve it, but I just can’t download. It’s likely a routing or firewall issue at this point.
I don’t use ATT’s DNS, I use Cloudflare GW from my own personal Org in Cloudflare.
Comparing DNS blocking methods disagrees, but yours might not be by DNS.
EDIT 1:
… for reasons you stated, however there are others who think theirs was DNS.
Please see what ATT support says.
Looks like it was a route issue. This is resolved for me.
Thank you for all the help and troubleshooting. I am now more familiar with Duplicati’s backend and how to troubleshoot issues more effectively.
2 Likes