lixingcong
commented
1 year ago Please provide git commit, your full config file and run dnsmasq with -q -d to see what happen
For example:
Commit https://github.com/lixingcong/dnsmasq-regex/commit/c40a35d921bcb7ba027fdd3e182156bf160ca09a
# config file is /tmp/dnsmasq-example.conf
port=30000
server=1.1.1.1
server=/\.edu/8.8.8.8Run command
./dnsmasq/src/dnsmasq -C /tmp/dnsmasq-example.conf -q -dRun dig from another terminal
dig @localhost -p 30000 1.eduPost your dnsmasq log
dnsmasq: started, version 2.87 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n regex no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-cryptohash no-DNSSEC loop-detect inotify dumpfile
dnsmasq: using nameserver 1.1.1.1#53
dnsmasq: query[A] 1.edu from 127.0.0.1
dnsmasq: forwarded 1.edu to 8.8.8.8
dnsmasq: reply 1.edu is NXDOMAIN
leodexe
I have setup a list of allowed domains which previously worked on official dnsmasq like this: [dnsmasq.conf]
# AdGuard IPv4/IPv6 nameserversserver=140.90.14.15server=140.90.15.16server=2a10:50c0::bad1:ffserver=2a10:50c0::bad2:ff[blocklist.conf]
address=/*/#server=/*.edu/#server=/*.io/#server=/*.org/#The first address line blocks everything, so each individual domain that does not end in .edu, .io or .org needs to be unblocked manually, which is how I have configured my dnsmasq blocklist as you will see below, normally it would look like this:
server=/*abc.com/#non-regex addresses like the three server lines after the address line works fine, however, when I use the regex syntax, the hashtag symbol (#) that normally redirects to the nameservers I previously configured stops working, along with dnsmasq built-in subdomain wildcard () support, which would accurately unblock both abc.com and subdomains of .abc.com, while also preventing any typos from being unblocked like aabc.com and abcabc.org, etc. According to Perl Syntax described here, the [^...] metacharacter should match anything that's NOT within the brackets, this is required so the pattern can have more specificity and thus avoid blocking the previous examples of typos, see this Squid ERE regex syntax for example:
^.*\.?[^a-zA-Z0-9](keyword1|keyword2)\.[a-zA-Z]{2,}.*$This Squid url_regex pattern blocks every keyword that's included in the pattern, the dnsmasq-regex equivalent which uses PCRE syntax should look something like this:
server=/:.*[.]?[^\w]abc[.]:/#However since the hashtag (#) symbol stops working properly as previously stated, I have to manually specify the nameservers I already configured which can be quite cumbersome as I have many many domains that redirects to the default nameserver:
server=/:.*[.]?[^\w]abc[.]:/1.1.1.3This does not work as expected, removing the [^\w] from the pattern will give unintended matches like aaaaaaaaaabc.com which is why it must be there to accurately block only the specified domain, but is the closest thing to a functional pattern.
I have compiled dnsmasq-regex with the options that are enabled by default on official dnsmasq package which are:
#define HAVE_DBUS#define HAVE_CONNTRACK#define HAVE_IDN#define HAVE_LIBIDN2#define HAVE_NFTSET#define HAVE_DNSSECSince without HAVE_DBUS enabled, the new compiled dnsmasq-regex completely fails to launch, the others are also there because they already come with standard dnsmasq, so just for precaution I added them back.
Last but not least, check this