On Mon, 6 Dec 2021 14:20:51 +0100 Sven Mueller <sven.muelle...@gmail.com> wrote: > Package: dnsmasq > Version: 2.86-1.1 > Severity: Serious > > We have this our /etc/NetworkManager/dnsmasq.d/local-proxy: > > local=/in.ourdoma.in/127.0.1.1#10053 > > This leads to: > > dnsmasq: Bad address in --address at line 2 of > /etc/NetworkManager/dnsmasq.d/goobuntu-dnsproxy > > The syntax used is exactly as documented in `man dnsmasq`: > /domain/server#port > > Once I remove the port (#10053), the configuration "works" (except that it > of course doesn't find the server to resolve the relevant requests).
Is that regression specific to 2.86-1.1 i.e. is my backport of the fix for [1] incomplete/broken or did you experience the problem with 2.86-1 as well? Looking at the upstream git repo and its log, there might be other fixes which need to be cherry-picked or we simply wait until Simon makes a 2.87 release :-) [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 [2] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git
signature.asc
Description: This is a digitally signed message part
