Re: [Dnsmasq-discuss] priority of local= and ipset=
I just did some test. looks like the 'google.com' will be send to both 1.1.1.1 and 8.8.8.8. but the all the resolved ip address will only be added to ipset 'one' On Tue, Jan 4, 2022 at 2:20 PM Justin wrote: > > Hello > i have settings in the order like this in dnsmasq.conf > > local=/google.com/1.1.1.1 > local=/google.com/8.8.8.8 > ipset=/google.com/one > ipset=/google.com/two > > what is the behavior of dnsmasq? which nameserver will be uses to > resolve google.com and which set name will the resolved ip of > google.com be added to? > > thanks. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] reducing DNS packet size for nameserver 127.0.0.1 to 1280
Recently i see lots of logs in dnsmasq: reducing DNS packet size for nameserver 127.0.0.1 to 1280 almost one per minute my conf: pid-file=/var/run/masq.pid user=dnsmasq keep-in-foreground no-negcache no-resolv domain-needed no-poll dns-forward-max=1000 cache-size=1000 min-cache-ttl=3600 port=53 server=127.0.0.1#5353 dnsmasq is run by systemd: ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] reducing DNS packet size for nameserver 127.0.0.1 to 1280
dnsmasq is run by systemd: /usr/bin/dnsmasq -C /etc/dnsmasq.conf On Tue, Jan 4, 2022 at 5:34 PM Justin wrote: > > Recently i see lots of logs in dnsmasq: > reducing DNS packet size for nameserver 127.0.0.1 to 1280 > almost one per minute > > my conf: > > pid-file=/var/run/masq.pid > user=dnsmasq > keep-in-foreground > no-negcache > no-resolv > domain-needed > no-poll > dns-forward-max=1000 > cache-size=1000 > min-cache-ttl=3600 > port=53 > server=127.0.0.1#5353 > > dnsmasq is run by systemd: ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Infinite loop in dnsmasq v2.86?
On 2022-01-04 Simon Kelley wrote: > The only thing that sticks out in the config is dnssec-debug. Not > recommended to run that in production use. > As for debugging, the crucial thing, as always, is being able to > reproduce the problem with as little effect as possible. Once that's > done, building with > make CFLAGS=-g > and then running under gdb with the -d flag is a good simple way to start. [...] Hello, FWIW this looks similar to https://bugs.debian.org/1001576 which features a backtrace. cu Andreas ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] reducing DNS packet size for nameserver 127.0.0.1 to 1280
Hey Justin, On Tue, 2022-01-04 at 17:34 +0800, Justin wrote: > Recently i see lots of logs in dnsmasq: > reducing DNS packet size for nameserver 127.0.0.1 to 1280 > almost one per minute > > my conf: > [...] > server=127.0.0.1#5353 once per minute sounds like this is happening all the time (dnsmasq doesn't warn for one minute if it happened once). You should either increase the EDNS buffer size on the server running at 127.0.0.1#5353 or add the config line edns-packet-max=1280 to your config to adhere to the limit. Furthermore, What server is running on port 5353 of your machine? I suggest reading this discussion, Pi-hole runs dnsmasq at its heart and everything is directly applicable to your situation: https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803 Maximum packet sizes for some commonly used server are here https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31 Best, Dominik ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] Possibility to split lines for values in conf file
Hello, is there a possibility to split lines which have lots of value ? Something like \ terminator next line being next values or to be able to define multiple lines with same option ? I face the problem with static route like (one line in conf file) dhcp-option=lan,tag:ordi,121,172.18.0.0/16,172.16.30.254,192.168.18.0/24,172.16.30.254,172.20.0.0/16,172.16.30.254,192.168.20.0/24,172.16.30.254,172.22.0.0/16,172.16.30.254,192.168.22.0/24,172.16.30.254,172.24.0.0/16,172.16.30.254,192.168.24.0/24,172.16.30.254,192.168.46.0/24,172.16.30.254 for a better readability and understanding I would prefere something like dhcp-option=lan,tag:ordi,121,172.18.0.0/16,172.16.30.254,\ 192.168.18.0/24,172.16.30.254,172.20.0.0/16,172.16.30.254,\ 192.168.20.0/24,172.16.30.254,172.22.0.0/16,172.16.30.254,\ 192.168.22.0/24,172.16.30.254,172.24.0.0/16,172.16.30.254,\ 192.168.24.0/24,172.16.30.254,192.168.46.0/24,172.16.30.254 or dhcp-option=lan,tag:ordi,121,172.18.0.0/16,172.16.30.254, dhcp-option=lan,tag:ordi,121,192.168.18.0/24,172.16.30.254, dhcp-option=lan,tag:ordi,121,172.20.0.0/16,172.16.30.254, dhcp-option=lan,tag:ordi,121,192.168.20.0/24,172.16.30.254, dhcp-option=lan,tag:ordi,121,172.22.0.0/16,172.16.30.254, dhcp-option=lan,tag:ordi,121,192.168.22.0/24,172.16.30.254, dhcp-option=lan,tag:ordi,121,172.24.0.0/16,172.16.30.254, dhcp-option=lan,tag:ordi,121,192.168.24.0/24,172.16.30.254, dhcp-option=lan,tag:ordi,121,192.168.46.0/24,172.16.30.254 The final comma meaning next same option is to concatenate with previous one (if any). Waiting your comments -- Daniel ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] reducing DNS packet size for nameserver 127.0.0.1 to 1280
Thanks Dominik the program runs at 5353 is chinadns-ng, it acts as a dns dispatcher and it's upstream is set to 8.8.8.8 or 1.1.1.1. this table is very helpful, it says 8.8.8.8 max at 1400, 1.1.1.1 max at 1452. https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31 but the log only showed recently, after Dec 24th. this is weird. On Wed, Jan 5, 2022 at 01:51 Dominik Derigs wrote: > Hey Justin, > > On Tue, 2022-01-04 at 17:34 +0800, Justin wrote: > > Recently i see lots of logs in dnsmasq: > > reducing DNS packet size for nameserver 127.0.0.1 to 1280 > > almost one per minute > > > > my conf: > > [...] > > server=127.0.0.1#5353 > > once per minute sounds like this is happening all the time > (dnsmasq doesn't warn for one minute if it happened once). > > You should either increase the EDNS buffer size on the server > running at 127.0.0.1#5353 or add the config line > > edns-packet-max=1280 > > to your config to adhere to the limit. > > Furthermore, What server is running on port 5353 of your machine? > > I suggest reading this discussion, Pi-hole runs dnsmasq at its > heart and everything is directly applicable to your situation: > > https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803 > > Maximum packet sizes for some commonly used server are here > > > https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31 > > Best, > Dominik > > -- Regards Justin He ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
