Already tried removing cookies and cache data, and it didn’t fix it
It works on Google Chrome and Firefox browsers and in Gnome Maps application, so not an ISP problem
The same occurs in a private window.
I’ve seen lots of posts about this, in one someone said clearing the cache solved for him, but it didn’t do a thing in my case, all of those seem to be dismissed. And I can comment on them.
This problem has been present since I started using brave, I’ve seen lots of similar posts, always the same suggestions from the staf and it never helps. It seems to be a bug in brave, otherwise please tell me what was I doing wrong, considering that I already tried all variants suggested, and all of that is in this description
Update: it happens the same in the snap version, without any customization, and the location detected is the same as the deb distributed version.
Yup, got it, you explained that already. But the point here isn’t any ‘DNS leak’ itself, but to see if we can ferret out a difference in the way your DNS lookups are being performed. As I said, it’s going to be challenging unless you are able to review everything relevant directly on your end.
The way DNS-based geolocation normally works is an authoritative name server determines your location based on a client subnet as perceived by your DNS resolver, for example Google Public DNS. And it can then change the web servers you target based on that; this doesn’t necessarily translate into the web site serving you different content (i.e. a different map location in this case), but a different DNS resolver result would be an indirect means of showing that in Browser X you are seen as coming from a certain IP, whereas in Browser Y it’s a different IP.
Hi @Saoiray, anything else you think it could help solve this problem?, judging for the other ones posting the same issue, it does not only happen in linux, but also in windows. None of the topics I found had a satisfying closure. All of them were closed by timeout.