# file, getting its servers from this file instead (see below), then # If you don't want dnsmasq to read /etc/nf or any other # Never forward addresses in the non-routed address spaces. # Never forward plain names (without a dot or domain part) # these requests from bringing up the link unnecessarily. If you have a dial-on-demand link they also stop # answer, and which load the servers (especially the root servers) # tell dnsmasq to filter out queries which the public DNS cannot # The following two options make you a better netizen, since they # If you want dnsmasq to read another file, as well as /etc/hosts, use
NXFILTER 127.0.0.1 SOFTWARE
# the Free Software Foundation, either version 2 of the License, or
NXFILTER 127.0.0.1 LICENSE
# it under the terms of the GNU General Public License as published by # Pi-hole is free software: you can redistribute it and/or modify # Network-wide ad blocking via your Raspberry Pi Just as if dnsmasq is getting some other config.ĩnf # Pi-hole: A black hole for Internet advertisements
NXFILTER 127.0.0.1 UPDATE
Srv-host=_wpad._tcp.192.168.1.2,wpad.192.168.1.2,80Īfter last update of pi-hole for some reason dnsmasq totaly ignores these settings # This allows it to continue functioning without being blocked by syslog, and allows syslog to use dnsmasq for DNS queries without risking deadlockĪddress=//192.168.1.2 # server for potentially stale date, you can set a time-to-live (in If you are happy to trade lower load on the # file have Time-To-Live set as zero, which conventionally means # Normally responses which come from /etc/hosts and the DHCP lease # For debugging purposes, log each DNS query as it passes through # Or which to listen on by address (remember to include 127.0.0.1 if # specified interfaces (and the loopback) give the name of the Need to insulate dnsmasq to eth0 otherwise nxfilter can not use port 53 on eth4.Ġnf: # If you want dnsmasq to listen for DHCP and DNS requests only on I have nxfilter running on eth4 on the same box. Perhaps an extra include in nf for custom user settings? Q2: is there an option to keep my settings with future updates, as pihole update destroys custom dnsmasq settings.everytime. etc.) and keep pihole working also off course. Q1: how can I edit dnsmasq settings so I can re-enable my custom settings: I did read a post about nf, but that layout is not suitable for adding my settings. Now I noticed with version 2.9.4 (pihole -up=> keep settings) somehow I am no longer able to edit dnsmasq settings to enable my custom settings. In the past, after updating pihole, to restore my personal dnsmasq settings was to overwrite 01.nf with my former one.
Running raspberry and using dnsmasq to serve dhcp.(and a whole lot off other stuff like privoxy and also nxfilter on a second network interface) I got away with updating to pihole 2.9.2 and have all running without any issues.
0 kommentar(er)
