https://github.com/jipok/dnsr
DNS-based selective routing for DPI bypass on Linux & routers
https://github.com/jipok/dnsr
anticensorship dns-proxy go linux nfqueue openwrt proxy router socks5 wireguard zero-configuration
Last synced: 4 months ago
JSON representation
DNS-based selective routing for DPI bypass on Linux & routers
- Host: GitHub
- URL: https://github.com/jipok/dnsr
- Owner: Jipok
- License: mit
- Created: 2024-08-07T12:02:48.000Z (about 1 year ago)
- Default Branch: master
- Last Pushed: 2024-11-01T20:50:46.000Z (11 months ago)
- Last Synced: 2025-06-23T02:07:19.160Z (4 months ago)
- Topics: anticensorship, dns-proxy, go, linux, nfqueue, openwrt, proxy, router, socks5, wireguard, zero-configuration
- Language: Go
- Homepage:
- Size: 68.4 KB
- Stars: 23
- Watchers: 2
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# DNSR (DNS Router)
> [!NOTE]
> **Major Update (4.0)**:
> - Now uses DNS-based routing instead of transparent proxy
> - Better performance and reliability, especially on routers
> - If you need SOCKS5 proxy support, use old [v3 release](https://github.com/Jipok/dpi-bypass-proxy/releases/tag/3.0.0)
A simple yet powerful tool that automatically routes your traffic through VPN for blocked websites while keeping everything else direct. Just download, run, and enjoy unrestricted internet access! Perfect for both personal computers and **routers**.
## Key Features
- ✨ **Simple to Use**: Download and run - that's it!
- 🌐 **Universal**: Works on both Linux PCs and routers (OpenWrt)
- 🚀 **Smart Routing**: Only routes specified websites through VPN, keeping other traffic direct
- ⚡ Lightweight: Minimal resource usage with maximum efficiency
- 🔧 Built-in WireGuard support (can automatically set up from config)
- 🛡️ Optional domain blocking
- 🔄 Auto-cleanup on exit
- 📝 Support for OpenVPN, WireGuard, or any other network interface
## Quick Start (2 Minutes Setup)
1. Download the [latest release](https://github.com/Jipok/dpi-bypass-proxy/releases/latest) or build from source
2. Prepare your domain lists:
```bash
# For proxy list (recommended)
wget https://github.com/1andrevich/Re-filter-lists/raw/refs/heads/main/domains_all.lst -O proxy.lst
# For block list (optional)
wget https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/gambling/hosts -O blocks.lst
```
3. Run with either a WireGuard config or existing interface:
```bash
# Using WireGuard config (automatic setup)
sudo ./dnsr ~/my-wireguard.conf
# Or using any existing network interface
sudo ./dnsr --interface tun0 # OpenVPN interface
sudo ./dnsr --interface wg0 # WireGuard interface
```
That's it! DNSR automatically handles everything else.
## OpenWrt Setup Guide
1. First, check your router's architecture to download the correct binary:
```bash
uname -m # or
opkg print-architecture
```
2. Download the appropriate binary for your architecture from the [releases page](https://github.com/Jipok/dpi-bypass-proxy/releases/latest).
3. The DNSR requires the NFT queue kernel module. Install it using:
```bash
opkg update
opkg install kmod-nft-queue
```
4. Start dnsr
5. Once DNSR creates its network interface, you'll need to configure a new firewall zone:
Click to see firewall zone configuration
### Command Line Options
```
Usage: dnsr [--interface INTERFACE] [--proxy-list PROXY-LIST] [--block-list BLOCK-LIST]
[--silent] [--verbose] [--no-clear] [WG-CONFIG]
Positional arguments:
WG-CONFIG Path to WireGuard configuration file (optional)
Options:
--interface, -i Use existing network interface (OpenVPN, WireGuard, etc.)
--proxy-list Domains to route through specified interface [default: proxy.lst]
--block-list Domains to block [default: blocks.lst]
--preset-ips File with IP addresses to proxy immediately, without waiting for DNS resolution
--silent, -s Don't show when new routes are added
--verbose, -v Enable verbose output
--persistent, -p Keep WireGuard interface (if created) and routes after exit
--help, -h Show this help message
--version Show version
Multiple proxy/block/ips lists can be specified using semicolon (;)
Example: proxy1.lst;proxy2.lst;proxy3.lst
```
## How It Works
1. The tool monitors DNS responses using NFQUEUE
2. When a domain from the proxy list is resolved:
- Creates specific routes for the resolved IP addresses
- Directs matching traffic through specified interface
3. All other traffic continues to use the default route
4. Domains in the block list are dropped