dns.resolver.override_system_resolver doesnt work in windows

[AliGhaffarian]

Describe the bug
either i dont understand the purpose of the function or this really doesnt work
i wanted to get the resolution of a domain from a dns server i chose not the system so i looked it up in the doc and this seemed to be my answer

To Reproduce
resolver.override_system_resolver("178.22.122.100")
resolver.resolve("epicgames.com", "A")
then i can clearly see that epicgames.com is resolved by my systems dns server ( via wireshark )

Context (please complete the following information):

• latest version currently present in pip
• Python 3.11.9
• OS: Windows 11 Pro 23H2

[AliGhaffarian]

i tried running the python3 as admin but no difference

[rthalley]

The purpose of override_system_resolver() is changing what socket.getaddrinfo() and related Python system DNS functions work. Normally they use the system's default resolver. Sometimes you may want to have different resolution policies affect Python code that is not aware of dnspython, and this is how you do it.

To do what you are trying to do, you do this:

import dns.resolver

dns.resolver.resolve_at("1.1.1.1", "amazon.com", "A")

or if you're going to be doing a bunch of queries to the resolver, you could do this:

import dns.resolver

my_resolver = dns.resolver.make_resolver_at('1.1.1.1')
my_resolver.resolve("amazon.com", "A")
my_resolver.resolve("epicgames.com", "A")

[zarquon5]

Unfortunately, this makes a big assumption on why one would replace the system resolver with a custom one. Our use case is to add both caching and timeouts for DNS resolutions, to make it more resilient to network issues and ensure realtime behavior without indefinite blocking on DNS. However, we want to maintain the processing order of how resolution normally works.

We discovered (painfully) that this doesn't happen, because the original system socket.getaddrinfo() performs resolution in two steps: it does local resolution on the machine, including (but perhaps not limited to) addresses mapped in the hosts file, followed by using DNS iff the address has not yet been determined locally. By replacing the socket methods, (at least on Windows) you're effectively preventing the system32/drivers/etc/hosts file from being honored because all the logic for doing that is buried in the underlying _socket() object is not either replicated (or not functioning) in your replacement methods.

So now we're scrambling to figure out of there's anything that can replicate the local resolution processing outside of the socket library methods, so we can update our custom resolver with it and still use dnspython.

Any suggestions?