1.1.1.1 is using the farest server for my location

I live in the north of Brazil, and the nearest DNS server for my location is the server (Fortaleza, BR), but I’m getting from (São Paulo, BR) instead, I should be getting DNS resolve from ‘Fortaleza’ which is among 23ms against 50ms of ‘São Paulo’, it’s strange, cuz’ in the status servers location everything seems to be working fine with Fortaleza server. I hope you guys fix this problem with my location, be getting the farthest server instead of the nearest

Oh, I’m sure there are servers farther away than 50ms.

2 Likes

I live in Austria (Europe) and use WireGuard and Cloudflare WARP+.
Cloudflare WARP+ is assigning me a New York (USA) public IP. (8.20.127.27)
I’m using 192.168.1.1 as DNS (running unbound on my router).
When I’m using 1.1.1.1 as DNS, I get a local (Munich) puplic IP.
I want to use my own, local DNS.(192.168.1.1)
How can I resolve this?

Edit:
I can provide account_id, access_token, private_key, public_key, or license_key if needed.
Or 1.1.1.1/help link.
https://cloudflare.com/cdn-cgi/trace also states:
colo=MUC
loc=AT

Edit2:
After disabling and enabling my WireGuard connection 10x, I suddenly got a local (Munich) public IP.
How can I control this?

Edit3:
After a computer restart, I’m bach to an US based public IP again. After disabling and enabling my connecion 20x I gave up…