[Dnsmasq-discuss] ipset add ipv6 address to ipv4 sets.

2022-01-08 Thread Justin
So. i have local=/google.com/8.8.8.8 ipset=/google.com/proxy when "curl google.com" dnsmasq log shows: ipset add proxy 142.250.217.142 google.com ipset add proxy 2607:f8b0:4007:818::200e google.com looks like dnsmasq does not check the SETNAME "proxy" is ipv4 or ipv6. so "ipset add proxy

Re: [Dnsmasq-discuss] strict-order with no-resolv; multi ignore-address

2022-01-08 Thread Justin
3) --all-servers says: By default, when dnsmasq has more than one up‐ stream server available, it will send queries to just one server. --strict-order says: By default, dnsmasq will send queries to any of the upstream servers it knows about and

[Dnsmasq-discuss] strict-order with no-resolv; multi ignore-address

2022-01-08 Thread Justin
Hello I have 2 questions: 1) if no-resolv is set, will stric-order apply to server=dns1 server=dns2 ... on man page, it only mentions /etc/resolv.conf 2) can i have multiple ignore-address= ? -- Regards Justin He ___ Dnsmasq-discuss mailing

[Dnsmasq-discuss] [PATCH] Addressing hostsdir shortcomings

2022-01-08 Thread Dominik Derigs
Hey Simon, dnsmasq v2.73 added --hostsdir which is an efficient way of re- loading only parts of the cache. When we tried to use hostsdir yesterday, we identified three problems. They are described below. Patches addressing them are attached. --- ISSUE 1 --- Logging imprecision Assume you have

[Dnsmasq-discuss] [PATCH] Improve cache dump

2022-01-08 Thread Dominik Derigs
Hey Simon, These patches improve the cache dump triggered by sending SIGUSR1. 1. The width of the host and address fields are 30 and 40 characters, respectively. Fix the header and add a head separation line to highlight how long the fields can be. 2. Add "!" as type for non-terminals, new flag

[Dnsmasq-discuss] [PATCH] Log server port when forwarding upstream

2022-01-08 Thread Dominik Derigs
Hey Simon, another patch: Log server port when forwarding upstream to avoid ambiguities when running multiple upstream destinations at the same IP but on different ports. The port is already logged in other places, like after starting dnsmasq: Nov 17 18:03:16 dnsmasq[123]: using nameserver