[Dnsmasq-discuss] dhcp-host ipv6 not get assigned yet ipv4 does

2024-10-19 Thread Glen Huang
I have this flag set dhcp-host=example,[::10],192.168.1.10 and my machine correctly gets 192.168.1.10 for ipv4, but gets a random ipv6 address from the dhcp-range flag. Seems the ipv6 in dhcp-host is simply ignored. Any idea why that could happen? Here is my full config: bind-dynamic bogus-priv

Re: [Dnsmasq-discuss] dhcp-host ipv6 not get assigned yet ipv4 does

2024-10-19 Thread Glen Huang
Forgot to mention, I use dnsmasq 2.90 on linux. On Sun, Oct 20, 2024 at 3:50 AM Glen Huang wrote: > > I have this flag set > > dhcp-host=example,[::10],192.168.1.10 > > and my machine correctly gets 192.168.1.10 for ipv4, but gets a random > ipv6 address from the dhcp-range flag. Seems the ipv6 i

Re: [Dnsmasq-discuss] Bug? no-negcache set but still instant status:REFUSE w/ EDE: 23 (Network Error).

2024-10-19 Thread mo via Dnsmasq-discuss
I guess, for now, it is dns-forward-max hit. And the counter never gets reset and/or the connections to upstream never get timeout/flushed because the REFUSED reply lasted much longer than 40s(the timeout in source code) while no request going in for that period. On Sat, Oct 19, 2024 at 9:54 PM チュ

Re: [Dnsmasq-discuss] Possible to enable DNSSEC only for specific upstream servers?

2024-10-19 Thread Kevin P. Fleming
On Sat, Oct 19, 2024, at 11:07, wkitt...@gmail.com wrote: > On 10/19/24 9:51 AM, Kevin P. Fleming wrote: >> Unfortunately when the 'general' usptream resolvers provided by the >> hotel/airplane/etc. don't provide RRSIG in their responses, I have to >> disable >> the global 'dnssec' setting in dn

Re: [Dnsmasq-discuss] Possible to enable DNSSEC only for specific upstream servers?

2024-10-19 Thread wkitty42
On 10/19/24 9:51 AM, Kevin P. Fleming wrote: Unfortunately when the 'general' usptream resolvers provided by the hotel/airplane/etc. don't provide RRSIG in their responses, I have to disable the global 'dnssec' setting in dnsmasq, otherwise all DNS resolution is broken. if they are using "wall

[Dnsmasq-discuss] Bug? no-negcache set but still instant status:REFUSE w/ EDE: 23 (Network Error).

2024-10-19 Thread mo via Dnsmasq-discuss
`dig foo.bar @127.0.0.1 -p 53`, 0ms instant return which upstream is at least 10ms away. But dig upstream the result is correct. Restarted dnsmasq it'll work for a while then error again. I'm on the latest git. Running a debug screen for now and want to get more info from dev. _

[Dnsmasq-discuss] Possible to enable DNSSEC only for specific upstream servers?

2024-10-19 Thread Kevin P. Fleming
I use dnsmasq on my OpenWrt-based travel router, and generally it works great. I want to enable DNSSEC validation for a domain that I operate, and to do that I've installed a trust anchor for the domain and configured a 'server' entry to route requests for that domain to a recursive resolver tha