Why does my NextDNS connect to this server when there is one closer?

Ruby Balloon Thank you for sharing your brains and experience with all of us sitting out here reading and learning also.  My setup is doing pretty darned good, stability wise. I'm just wondering how we can change from or use or even test ultra low latency IPs vs anycast IPs.  I have windows and don't see a way to change that in the client settings.  Thank you sir.

RDLMP FYI, it looks like something is not allowing the windows 2.01 client to connect,

I click enable and it just sits there. Never letting me enable it. 

Checking if windows defender or other AV is blocking it,

I turned OFF windows defender FW and it still is not allowing enable.

Windows 10 pro ver 2004 os build 19041.746

I added an exclusion to the entire folder and subdirectories of C:\Program Files (x86)\NextDNS

and it still is not enabling, I did see an error earlier that windows smartscreen blocked it once, I told it to allow it and still no difference. 

Just saying, I'm always the first to notice things not working and reporting, I am used to hearing 'sir, we have 900 other houses on your node of your cable modem, noone else is having an issue.  Then call back 2 hours later, an outage is being worked on in your neighborhood.  8 cox trucks, working on the main line, they admit they have noise, over capacity 8x the limit, 66% packet loss etc.

RDLMP the client DID install and seems to work fine on another computer that is NOT running 20H2 with the next round of windows updates coming up soon.  So others may not have issues til the second tuesday of next month.

I'd still like to know how We can find ultralow vs anycast Ips to change DNS to for example on the router,  I know, I know there's a lot of things with that,  Just testing the basics here 45.90.28.94 and 45.90.30.94 are what the portal say to use.  I'm wondering when 45.90.28.0 and 45.90.30.0 are appropriate.

I did have and report the issues on 45.90.30.x a few weeks back, noone acknowledged the issues of 110ms dns replies vs 22ms replies on 28.94 for example on the same network.  I saw the 30.x going to France from here in Tulsa, OK so that explained the 110ms dns replies.  It was mysteriously fixed and noone said boo.  which is fine.

It's nice to get noticed and told we're not nuts occasionally.

RDLMP It's mostly all done on the back-end. You cannot explicitly pick a server but if you or the OP is experiencing latency or non-ideal routing then you both can follow the steps via https://help.nextdns.io/t/y4hmvcx/report-network-latency-issue

They also usually want to know what setup your running which is why they tend to ask for your results of test.nextdns.io

But depending on your setup, you can toggle Ultra low latency (ULL) on the front-end. Ex, the windows setup "Yoga DNS" allows you to explicitly enable/disable ultra low latency (ULL) but that's assuming it's available and in production on the back-end in your geographic area. In some geographies, it's still in testing I believe