[Dnsmasq-discuss] config error is REFUSED (EDE: not ready) since v2.86
Geert Stappers
stappers at stappers.nl
Wed Sep 6 19:54:20 UTC 2023
On Wed, Sep 06, 2023 at 12:11:19AM -0400, Jack YAPI wrote:
> We do use dnsmasq 2.85 but any newer versions passed 2.85 result in "config
> error is REFUSED (EDE:not ready)".
> I saw a patch was made to handle the address type in
> https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q3/015644.html
copied to here:
| Apologies all.
|
| The
|
| --address=/#/......
|
| functionality got omitted in the 2.86 domain-search rewrite, which
| explains everything. Treating # as a domain name, it doesn't match
| the test domain, so dnsmasq tries to forward upstream. There are no
| upstream servers configured, so it returns REFUSED.
|
| I just pushed a pretty straightforward patch to fix this.
|
| Cheers,
|
| Simon.
>
> Can we have a similar patch to handle the server type as well. It looks
> like it's only grabbing # as domain without processing the ip address
> appended to it.
>
> In our case we are trying to start dnsmasq with
>
> dnsmasq -k -q \
> --log-facility=- \
> --log-debug \
> --cache-size=0 \
> --no-hosts \
> --no-resolv \
> --server=/#/x.x.x.x \
>
>
> with x.x.x.x is the ip address.
The IP-address of what?
> In the log we can see that it's referencing the domain as:
> for domain #
> config error is REFUSED (EDE:not ready)"
I haven't tried yet to reproduce the error.
I don't understand what the
> --server=/#/x.x.x.x \
is supposed to do. The \ seems to be lost, so am I :-)
Groeten
Geert Stappers
--
Silence is hard to parse
More information about the Dnsmasq-discuss
mailing list