[Dnsmasq-discuss] dnsmasq: /#/<ip> and error "config error is REFUSED (EDE: not ready)“
Geert Stappers
stappers at stappers.nl
Fri Sep 15 20:15:59 UTC 2023
On Tue, Sep 12, 2023 at 09:15:04PM +0200, Yann ILAS wrote:
> Le mar. 12 sept. 2023 à 18:56, Geert Stappers a écrit :
> > On Mon, Sep 11, 2023 at 01:58:07PM +0200, Yann ILAS wrote:
> > > Hi !
> >
> > Hello,
> >
> >
> > > I get an issue with version 2.89 of dnsmasq, on Debian 12. There seems to
> > > be a regression. I did see the changelog
> > > <https://thekelleys.org.uk/dnsmasq/CHANGELOG> for version 2.87, which
> > > states that the /#/ bug has been fixed... but I don't see it with version
> > > 2.89 (the last version installed on Debian). The /#/ in the config file
> > > seems still to be an issue.
> > >
> > > listen-address=127.0.0.1
> > > bind-interfaces
> > > server=/#/8.8.8.8
> > > server=/svc.cluster.local/10.96.0.10
> > > cache-size=500
> > >
> >
> > And with
> >
> > listen-address=127.0.0.1
> > bind-interfaces
> > server=9.9.9.9
> > server=/svc.cluster.local/10.96.0.10
> > cache-size=500
> >
> > ? (Yes, that are two changes!)
> >
> Hi,
>
> From the client :
> root at bookworm:~# dig @127.0.0.1 perdu.com A +short
> 172.67.133.176
> 104.21.5.178
>
> Log from the daemon :
> root at bookworm:~# dnsmasq --no-daemon --log-queries --log-debug
> dnsmasq: started, version 2.89 cachesize 500
> dnsmasq: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP
> DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC
> loop-detect inotify dumpfile
> dnsmasq: using nameserver 9.9.9.9#53
> dnsmasq: using nameserver 10.96.0.10#53 for domain svc.cluster.local
> dnsmasq: reading /etc/resolv.conf
> dnsmasq: using nameserver 9.9.9.9#53
> dnsmasq: using nameserver 10.96.0.10#53 for domain svc.cluster.local
> dnsmasq: ignoring nameserver 127.0.0.1 - local interface
> dnsmasq: read /etc/hosts - 7 names
> dnsmasq: query[A] perdu.com from 127.0.0.1
> dnsmasq: forwarded perdu.com to 9.9.9.9
> dnsmasq: reply perdu.com is 172.67.133.176
> dnsmasq: reply perdu.com is 104.21.5.178
Okay, that looks fine. Now test the two changes separately.
I refer to the above "Yes, that are two changes!"
Groeten
Geert Stappers
--
Silence is hard to parse
More information about the Dnsmasq-discuss
mailing list