Routing Legacy DNS to Ultralow instead of higher latency Anycast server?

Hi everyone,

I have a question regarding NextDNS routing, specifically concerning legacy DNS (standard UDP/50).

Currently, when using NextDNS's anycast IPs for legacy DNS (45.90.28.x and 45.90.30.x), my requests seem to be routed via anycast to a server that has higher latency for my location compared to NextDNS's ultralow latency network. I've confirmed through diagnostics that the ultralow servers offer a significantly better connection for me.

My main question is: Is it possible for legacy DNS requests (UDP/53) to be specifically directed or routed to the ultralow network servers, bypassing the standard anycast resolution that directs me to a higher-latency server?

I prefer using the legacy DNS IPs primarily because it greatly simplifies the setup across various devices on my network (like IoT devices, older systems, game consoles, etc.) which may not easily support DNS over HTTPS (DoH) or DNS over TLS (DoT). Ensuring all devices can easily use the NextDNS service via the standard DNS IPs is ideal for my setup.

I have diagnostic information (from nextdns diag or similar tests) showing the latency difference and the specific anycast server I'm currently hitting versus the available ultralow options. I can provide more details if needed.

Has anyone else faced this? Is there a known mechanism or configuration tweak within NextDNS to encourage or force legacy DNS traffic towards the ultralow infrastructure when it's demonstrably faster?

Any insights or suggestions would be greatly appreciated!

Thanks!

Link: https://nextdns.io/diag/b0ec4980-0cb3-11f0-9491-4961fd44a4fd