I'll try dnsmasq.static. As to why... I have installed pi-hole ( https://pi-hole.net/) on a VM and want to point clients at it as primary DNS, astlinux as secondary in case it fails. I configured pi-hole to use my astlinux as its primary DNS so all queries will ultimately go through astlinux, after pi-hole has done its thing to filter out the unwanted. No idea if I will keep this but thought I would give it a try and see if the family notices or if anything breaks.
David On Fri, Oct 19, 2018 at 4:54 PM Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: > > > > On Oct 19, 2018, at 3:44 PM, David Kerr <da...@kerr.net> wrote: > > > > I'm probably just overlooking it, but is there a way for me to define > the DNS servers that get pushed to clients in DHCP responses? Say I wanted > to push out 192.168.1.2 instead (or as well as) 192.168.1.1, how would I do > that? > > No trivial way. Possibly you could override the > "dhcp-option=lan,option:dns-server,.." value using /mnt/kd/dnsmasq.static . > > Which begs the question, Why ? :-) > > Lonnie > > > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. >
_______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
