How Super DNS Proxy Resolves Your DNS Queries
Super DNS Proxy is a local DNS proxy for Windows and Linux. Once it is running, your computer asks it for every domain name it needs and the app decides how that question gets answered. It listens on the loopback address 127.0.0.1, so a lookup never leaves your machine until the proxy has chosen which upstream resolver to forward it to.
What a DNS proxy changes
Normally your operating system sends each lookup to the DNS servers handed out by your network, which in most homes and offices means your ISP's resolvers. That works, but it leaves you with no control: you cannot see the lookups, you cannot change who answers them, and you cannot make a slow resolver faster. A proxy inserts itself into that path. You point Windows at 127.0.0.1, add the upstream DNS IP addresses you want to use inside the app, and from then on the app is the component asking them.
Every resolver is asked at once
Rather than picking a single resolver and hoping it stays responsive, you can list as many DNS IP addresses as you like: public resolvers, your own, or a mix of both. Each query is sent to all of them at the same time, and the first answer that comes back is the one returned to your machine. A resolver that is slow, overloaded or unreachable simply never wins the race, so it cannot hold up your browsing.
Queries that would otherwise be abandoned
Windows is quick to assume a DNS query was lost. When that happens it abandons the connection and the page you were loading stalls. The proxy waits 500 ms for a reply, an interval you can adjust, and then re-sends the query itself a set number of times, giving a slow resolver another chance before the lookup is allowed to fail.
The TCP port 443 reachability check
Some addresses resolve correctly and then turn out to be unreachable. With the check enabled, the proxy probes every returned address on port 443 before handing it back. If nothing responds within 200 ms it answers 127.0.0.1 instead, so your browser fails immediately rather than sitting on a dead connection waiting for a timeout.
DNS over TCP, sent as UDP
Chrome and Edge sometimes send DNS queries in the clear over TCP instead of the usual UDP. The proxy recognises those queries and turns them into UDP on the way out, which keeps them working with resolvers that expect ordinary DNS traffic.
What you can watch while it runs
A live query log shows every lookup as it happens, so you can see exactly what your machine is asking for. A live TCP retransmission log shows when a TCP SYN had to be re-sent before a server would answer, and it is available while the port 443 reachability check is switched off. An optional local DNS cache, off by default, keeps recently resolved names on your own machine for instant repeat lookups.
Getting started
Download the build for your operating system from the home page, extract it, unblock the executable on Windows, and launch it. Then set your Windows DNS server to 127.0.0.1 and add your upstream resolvers inside the app. The step-by-step notes for Windows and Linux sit on the home page, and the about page covers what the app is and where it fits in the BridgeMode network toolkit.