Windows 4.0.x Beta Tester - DNS Support

[Anof-cyber]

Domain-Based Proxy Rules #33

Download - ProxyBridge-Setup-4.0.8-Beta.zip

ProxyBridge rules can now match traffic by domain name - not just IP address and port.

Caution

This is the first feature in this project to be developed entirely by an AI model (Claude Opus 4.8), from the initial architecture and implementation plan to the final code. No manual code review has been performed yet.

This feature is introduced in v4.0.8-Beta and has only been tested against a limited set of basic use cases, where it behaved as expected. It has not undergone comprehensive testing, manual validation, or a security review, so bugs, edge cases, performance issues, or other unexpected behavior may still exist.

I'm looking for community testers to help evaluate this feature in real-world environments. If you encounter any bugs, unexpected behavior, or have suggestions for improvement, please open an issue or share your feedback.

Please consider this feature experimental and avoid relying on it in production until it has been thoroughly tested and manually reviewed.

Why this matters

Big services like Google, Cloudflare, or Netflix don't use a single IP. They spread across hundreds of constantly-changing CDN addresses. Trying to proxy them with IP rules is nearly impossible - you'd have to list every IP, and they change all the time.

With domain rules, you just write the domain once:

*.google.com

ProxyBridge follows that domain to whatever IP it currently resolves to. No need to track IPs.

How to use it

When you add or edit a rule, there's a new Target Domains field alongside Target Hosts and Target Ports.

Leave it as * for no domain restriction (default), or enter one or more domain patterns:

You type	It matches
* or empty	Any domain (no restriction)
google.com	Only google.com exactly
*.google.com	google.com and all its subdomains (www.google.com, mail.google.com, …)
*.google.com; *.gstatic.com	Multiple domains - separate with ; or ,

Domain matching is case-insensitive, and *.google.com also covers the plain google.com.

A rule matches only when everything matches - the process, the host, the port, and the domain. So you can combine them, or use a domain rule on its own (leave Hosts and Ports as *).

Example

Route all Google traffic through your proxy, no matter which IP it uses:

• Applications: chrome.exe
• Target Hosts: *
• Target Ports: *
• Target Domains: *.google.com
• Action: Proxy

Limitations

Domain rules work by watching your apps' normal DNS lookups. A few things to know:

• Encrypted DNS (DoH / DoT): If your browser or app uses "Secure DNS" / DNS-over-HTTPS, ProxyBridge can't see which domain is being looked up, so domain rules won't apply to it. Fix: turn off Secure DNS in the app, or use an IP/port rule instead.
• Just-added rules: When you add a domain rule, apps may already have the domain cached and skip a fresh lookup. ProxyBridge clears the Windows DNS cache automatically to help, but some apps keep their own cache - a browser restart or a moment's wait ensures new connections are matched.
• Unknown domains: If ProxyBridge hasn't seen the DNS lookup for a destination, a domain rule simply won't match it (your IP/port rules still work normally). Nothing breaks - it just falls through.