c1ay / dnsmasq-regex Goto Github PK

Lastest version: v2.89

patches:

• 001-regex-server.patch
• 002-regex-ipset.patch

Inspired by these repos:

• dnsmasq-regexp_2.76
• dnsmasq-regex

Original regex patch for dnsmasq 2.63

• using regular expressions in server list
• dnsmasq-2.63-regex.patch

Offical dnsmasq:

• dnsmasq

These packages were maintained by community. Build from source if your distribution was not in the list.

Package deatails: archlinux user repo

yay -S dnsmasq-regex

For Debian/Ubuntu:

# Install the dependencies
sudo apt install -y libpcre3-dev libnftables-dev pkg-config

# Clone the repo
git clone https://github.com/lixingcong/dnsmasq-regex
cd dnsmasq-regex

# update the sub-module 'dnsmasq' to latest version
# only update when a newer version is released
bash ./update_submodule.sh

# build it
make

# Run the binary, check if the compile option contains "regex(+ipset,nftset)"
./dnsmasq/src/dnsmasq --version

Tips: If you do not need the patch of ipset/nftables, just edit the file "Makefile" and build from source again.

Change this line

DNSMASQ_COPTS="-DHAVE_REGEX -DHAVE_REGEX_IPSET"

to

DNSMASQ_COPTS="-DHAVE_REGEX"

You could write regex line starts with ':' and ends with ':'

server=114.114.114.114
server=/google.com/8.8.8.8
server=/:myvpn[0-9]*\.company\.com:/1.1.1.1
server=/:a[0-9]\.yyy\.com:/#
address=/:a[0-9]\.xxx\.com:/127.0.0.1
ipset=/:.*youtube.*:/test
nftset=/:.*\.google.co.*:/ip#dnsmasq-table#google-ipset

The config above will:

• set default upstream server to 114.114.114.114
• match normal domain google.com then forward DNS queries to 8.8.8.8
• match domain myvpn[0-9]*\.company\.com then forward DNS queries to 1.1.1.1
• match domain a[0-9]\.yyy\.com then forward DNS queries 114.114.114.114 normally(default upstream server)
• match domain a[0-9]\.xxx\.com then return DNS record of localhost(to block ads?)
• add .*youtube.* query answers to ipset test
• add .*\.google.co.* query answers to nftables set, equivalent to nft add element ip dnsmasq-table google-ipset { 172.217.161.74 }

Here is a example config file: dnsmasq_regex_example.conf

Tips:

• A simple script to generate domains configurations: my-gfwlist

• The regex line [a-z]*gle\.com will match both google.com and google.com.hk. Use anchor ^ and $ to produce a more precise match.

Simon, the author of Dnsmasq, has rewritten the function to shorten the lookup time for queries. I have to rewrite the patch too. So the domain match function was changed.

If you upgrade from older version(2.85 or older), considering modify your config file. Maybe just simply move lines up and down.😉

The regex lines will generate a linkedlist to match(from top to bottom). If the domain matched both regex servers, DNS query will be forwarded the one which appears first.

Consider the config file below, the domain wx.qq.com will be forwarded to upstream 1.1.1.1, not 8.8.8.8

server=/:\.qq\.com:/1.1.1.1
server=/:\.qq\.com:/8.8.8.8

If the domain matched normal and regex servers, DNS query will be forwarded to the normal one.

Consider the config file below, the domain wx.qq.com will be forwarded to upstream 1.1.1.1, neither 8.8.8.8 nor 1.2.4.8

server=/:w\w?\.qq\.com:/1.2.4.8
server=/qq.com/1.1.1.1
server=/:\.qq\.com:/8.8.8.8

Please check this page: dnsmasq-regex-openwrt