B2 backup never times out if domain is blocked

I discovered this overnight after some pi-hole list ended up adding a backblazeb2 dot com subdomain resulting in 25k blocked dns queries by morning (roughly one per second). My backup script was just sat in the initial ‘snapshots’ command I use to validate the repo connection.

I presume this sort of issue likely affects the other cloud providers as well, but should there some sort of timeout and warning/error output when encountering this sort of thing? It also doesn’t seem to scale back the query rate over time either, it just keeps on requesting at a constant rate.

As an FYI the lists in question are:


You don’t need a pi-hole to replicate the issue, you can just add a temporary hosts file entry to for whichever domain it expects to connect to.