Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Connecting to wrong Onshape server
john_robinson568
Member Posts: 15 ✭
I started getting a warning icon appear on the Performance icon on the left side of the screen. When I expand the section, I can see that I am connected to "us-west-2", however I'm in Australia, and should be connecting to "ap-southeast-2". The US server gives me a latency of 160ms! I switched ISPs on Monday. and that's the only thing I can think of that might have caused this. I've done some googling and it appears that Onshape selects the region automatically. Is there anyway that I can force it to use a specific region? I'm at a bit of a loss here, I don't understand how changing ISP could cause this. and to be clear, I'm not saying that changing ISP DID cause this, I'm just saying that this started happening around the same time and it's the only thing I can think of that might have had an impact.
Any advice very much appreciated
Best Answers
-
john_rousseau
Member, Onshape Employees, Developers Posts: 393 
Hi @john_robinson568. Changing your ISP is almost definitely what caused this.
The DNS resolver that you are now using (https://www.top10vpn.com/tools/what-is-my-dns-server/ will show you what it is) is not indicating to the DNS server (AWS Route53) that you are in Australia. That's most likely because the DNS resolver is not near your actual location.
Try configuring a DNS resolver that's in AU. You can also use a global DNS resolver like 8.8.8.8 (Google) that supports EDNS client subnet.
What you don't want to be doing is using a DNS resolver that's far away from you, or a global one like Cloudflare (1.1.1.1) that doesn't support EDNS client subnet.
John Rousseau / VP, Technical Operations / Onshape Inc.2
Answers
It is highy likely that it's a configuration from your ISP, but I'll let @john_rousseau chime in.
Thank you @NeilCooke. It just occurred to me that using a VPN would probably be a good stop gap solution, so long as I use a local server. I might give that a go in the meantime
Hi @john_robinson568. Changing your ISP is almost definitely what caused this.
The DNS resolver that you are now using (https://www.top10vpn.com/tools/what-is-my-dns-server/ will show you what it is) is not indicating to the DNS server (AWS Route53) that you are in Australia. That's most likely because the DNS resolver is not near your actual location.
Try configuring a DNS resolver that's in AU. You can also use a global DNS resolver like 8.8.8.8 (Google) that supports EDNS client subnet.
What you don't want to be doing is using a DNS resolver that's far away from you, or a global one like Cloudflare (1.1.1.1) that doesn't support EDNS client subnet.
Thanks to all that replied. I checked my router's configuration, and the DNS name server was set to my new ISP default of 202.142.142.142. I did a few searches, and it all comes back to Aussie Broadband (my ISP), registered in Victoria Australia (where I am), but I don't know enough about DNS fto be able to do any more digging. I swapped the name servers over to google (8.8.8.8 and 8.8.4.4), and after a reboot, that fixed the problem! My latency is back down to 22ms.
Thanks very much once again for the very speedy and very helpful replies.