Re: [Dnsmasq-discuss] typo in dnsmasq.8 man page

On Wed, May 03, 2023 at 05:04:52AM +0800, Justin wrote: > https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob;f=man/dnsmasq.8;h=30429dfa84457af04651269b785aa8a8141265de;hb=HEAD#l393 > > diff > a comma-separated list or RR-types > a comma-separated list of RR-types At https://lists.thekelleys.o

Re: [Dnsmasq-discuss] dnsmasq sending advertise packets for the packet containing server id

Hi Simon, While validating the RFC 3315 standards through the test suite caught this issue. Thanks, Shashi On Tue, May 2, 2023 at 4:05 AM Simon Kelley wrote: > On 24/04/2023 05:41, shashikumar Shashi wrote: > > Hi, > > > > I am using dnsmasq-2.80, IN this I am observing dnsmasq sending the > >

[Dnsmasq-discuss] typo in dnsmasq.8 man page

https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blob;f=man/dnsmasq.8;h=30429dfa84457af04651269b785aa8a8141265de;hb=HEAD#l393 diff a comma-separated list or RR-types a comma-separated list of RR-types Regards Justin He ___ Dnsmasq-discuss mailing list

Re: [Dnsmasq-discuss] typo in dnsmasq.8 man page

by the way, CHANGELOG does not mention --cache-rr ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss

Re: [Dnsmasq-discuss] Implement --no-dns-interface?

I think you can use --bind-interfaces and --listen-address 127.0.0.2 to listen only on alternate address. On 21. 04. 23 3:18, Tony Zhou wrote: Hi, I am running dnsmasq 2.86 on openwrt, and have multiple vlans in my network. dnsmasq works great for dhcp purposes (for both dynamic and static l

Re: [Dnsmasq-discuss] --server=/#/1.2.3.4 behavior

On 26.04.23 14:26, Aleksey Vasenev wrote: I found some information in the changelog: "Of course --server=/#/1.2.3.4 is exactly equivalent to --server=1.2.3.4. Special request from Josh Howlett." But this is not true. --server=/#/1.2.3.4 takes precedence over --server=1.2.3.4. Moreover, other

Re: [Dnsmasq-discuss] use-stale-cache may failed to refresh record from certain upstream

sorry, the quote was wrong. the stale cache issue is confirmed fixed with the patch. i meant to quote this: *I think I've found and fixed the problem, but I don't have a macOS machine to test with, nor have a I configured a DOH proxy, so I'd appreciate it if you could re-run your

Re: [Dnsmasq-discuss] use-stale-cache may failed to refresh record from certain upstream

Hello Simon *Reply your message * *Thanks for the report. I've just pushed a code change which improves the checking of received packets to conform better with section 15.https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=7500157cff8ea28ab03e6e62e0d1575e4d01746b