family-dns: need per zone controls
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @farmergreg
Environment: x86_64, generic, HEAD (83cb2f4dc8)
Description:
I have a firewall with 3 different VLAN's behind it, via several Ubiquiti AP's, each VLAN being associated with a different SSID.
I'd like to only intercept/DNAT DNS requests on lan2 (aka eth0.2). It would be nice to be able to pick and choose which interfaces/zones that family-dns affects, as the kids at home have their own SSID to use with different rules, from the rest of the household.
It would also be nice to see it work not just with dnsmasq, but with isc-dhcp as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the family-dns package and examining how it currently integrates with dnsmasq. Trace how interfaces or zones are selected, then determine the scope needed for per-zone controls and isc-dhcp support. Done means DNS interception can be limited to selected zones and the requested DHCP integration works.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100