That is great news, I'm glad we've identified the root cause of the
problem and you have successfully resolved it.
I will mark this bug as invalid since, while the dnsmasq update did
change behaviour, the behaviour change revealed a configuration issue
rather than being an actual regression.
Your suggestion to limit bind will work for me.
I wasn't sure how to tell bind to not listen on an interface.
Bind defaults to: listen-on { any; };
I modified /etc/bind/named.conf.options by adding the following line:
listen-on port 53 { 127.0.0.1; 192.168.2/24; };
This should restrict bind
So, it looks like you are running bind on this machine, and bind is
listening on port 53 UDP:
udp0 0 192.168.122.1:530.0.0.0:*
1521/named
The old dnsmasq would ignore the error when it couldn't bind to a port,
but the new dnsmasq will fail if the port is already used, which
Attached txt file for output of netstat command ... first with dnsmasq-
base v 2.90-0ubuntu0.22.04.1 and then with previous version 2.86-1.1
If I look at the output from the ifconfig command, the virbr0 device is listed
when v2.86-1.1 is used. The virbr0 device is not listed when rebooting
What's the output of "sudo netstat --tcp --udp --listening --programs
--numeric"? Thanks!
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
(Note: New bug #2055776 opened a couple hours ago that looks related to
this issue)
For the following answers to your queries, I used both the new and
previous versions of dnsmasq-base with identical results:
What's the contents of the /etc/dnsmasq.d directory?
There is a symbolic link in this
This may be caused by the same issue as bug 2055776. I am preparing
updated packages with the problematic commit reverted for testing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Thanks for taking the time to make this bug report to make Ubuntu
better!
I tried reproducing your failure and unfortunately am not able to in a
VM/container setup. I think this may need some extra configuration to
reproduce the failure.
Starting with something basic, would you mind sharing
I must've opened this bug up in the morning before Marc commented and
just got back around to posting the question. Apologies for asking for
the same information!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in
Hi,
What the contents of the /etc/dnsmasq.d directory?
Is there a symlink to /etc/dnsmasq.d-available/libvirt-daemon ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
10 matches
Mail list logo
