On Wed, Sep 02, 2026 at 20:29:55 -0400, Robert Heller wrote: > The other *weirdness* is that the dig command returns *different* > IP address for the server listed in the Brave Browser repository config file > -- it seems to depend on geography and/or ISP path to the Internet backbone > (some DNS magic going on here). > > What is going on?
Well, the first thing you'll want to try is using something that queries hosts the same way apt does, rather than using dig, which exclusively uses DNS. It's possible you've got a line in your /etc/hosts file or something else which overrides DNS, which dig would not care about, but apt would. Canonically, you can use getent hosts ... instead of dig. There are lots of other choices as well. > heller@DebianServer:~$ sudo apt update > Get:1 http://mirror.llg.one/debian trixie InRelease [140 kB] > Hit:2 http://mirror.llg.one/debian trixie-proposed-updates InRelease > Err:3 https://brave-browser-apt-release.s3.brave.com stable InRelease > 403 Forbidden [IP: 3.167.37.65 443] Here's what I get: hobbit:~$ getent hosts brave-browser-apt-release.s3.brave.com 3.170.51.70 d9owkidwx4k9e.cloudfront.net brave-browser-apt-release.s3.brave.com 3.170.51.27 d9owkidwx4k9e.cloudfront.net brave-browser-apt-release.s3.brave.com 3.170.51.36 d9owkidwx4k9e.cloudfront.net brave-browser-apt-release.s3.brave.com 3.170.51.24 d9owkidwx4k9e.cloudfront.net brave-browser-apt-release.s3.brave.com Of course, that's not proof of anything misconfigured on your end, as the full set of IP addresses may not be served up on every request. If you're convinced you haven't accidentally overridden DNS with a line in the hosts file, or some other equivalent, then the only thing I can suggest is that you wait a few minutes and try again. For whatever it's worth, I'm also using Brave via their apt repositories, and I haven't seen this problem.
