The advantage for dnsmasq for myself is I’d already worked out a nice modular configuration for various features / controls that I’d wanted to set up, using dd-wrt. The main problem was that storage was so limited on the former router that I had to extensively pare down the blocklist(s). Mostly by putting higher-level blocks (e.g., domain rather than host) on domains with many, many listed entries.
It’s possible to define sets of configuration files, so I did:
00-master
01-basics
10-dhcp-hosts
12-custom
20-adblocking
21-addn-hosts
22-adblock-holes
23-mastodon-holes
24-sci-hub
25-bulkdomains
27-ads-n-banners
29-tld-blocks
… where 00-master listed the remainder. (You can also specify a config directory that obviates the need for the master file).
I’d manage that on my workstation under git and scp or rsync it to the router.
Files range from 9 - 1500+ lines. Breaking them out makes for much easier management.
Or, if I can do the equivalent under kresd / knot-resolver. I’m looking at those docs.