DNS for outlook.office.com, wrong geolocation in BE

What is the name of the domain?

outlook.office.com

What is the issue you’re encountering

Most of the time, our clients connect to Cape Town Africa with outlook because Cloudflare DNS sends us over there. Everything’s works very slowly because of this. When we are using other DNS providers, we are connected to Amsterdam, Paris of Germany. Everything works fast then. I add some screenshots.

What steps have you taken to resolve the issue?

Change DNS servers. But we don’t want to do that.

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

Resolve-dnsname in powershell, use of the Microsoft tool https://connectivity.office.com/

Screenshot of the error

1 Like

1 Like

Can you try running nslookup -type=txt -class=chaos id.server 1.1.1.1 to see at which location you connect to 1.1.1.1?

PS C:\data> nslookup -type=txt -class=chaos id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text = “BRU”

And when you try nslookup outlook.office.com 1.1.1.1?

always something different,
If you check the ip addresses, 52.98.23.242, it comes from Africa, others not.
Everytime I do a lookup, it is different.

I see it is not the first time:
Wrong geolocation for outlook.office.com from Belgium - Zero Trust / 1.1.1.1 - Cloudflare Community

2 Likes

@mvavrusa Any chance you could have a look at this again?

Did you changed something?
Maybe it has some time needed?
Now it is still like this, cleared my dns cache
2024-09-09_15h55_37

I don’t work for Cloudflare and can’t make any changes. I just mentioned the CF employee that fixed the problem in the topic you linked.

2 Likes

Ok, sorry,
Thx

Sorry for the issues, it seems like it’s still not correct at Microsoft’s side. I extended the workaround and will try to contact them again.

3 Likes

Hey,
Thx for the quick response and the workaround.
All my tests look good now, and we have a good connection to Amsterdam, Paris or Frankfurt now, no longer to Cape Town.
Can you explain a little bit what is not correct @ Microsoft’s side?
We have support @ Microsoft, we raised a ticket, but no clear answer.
I checked the network traffic and thought it was a DNS issue.
I will put this info in our Microsoft ticket.
Thx

1 Like

It’s a geo issue. When Cloudflare sends a DNS query to Microsoft’s nameservers from a source IP that’s in our Brussels pop, Microsoft DNS thinks the source IP is from or nearby Cape Town and returns the service address near there. The workaround on our side is to move these queries out of Brussels pop to other nearby pops which are geolocated correctly.

3 Likes

Thank you very much for the quick solution.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.