Thomas, please understand that I don't have the time to reiterate on situations that I have solved by reverting back to the original state. I gave you enough hints to solve the issue. You can set up a situation like mine in a bunch of virtual machines and simulate the effects.
I have a solution by disabling dnsmasq in network manager.
You might as well close this incident. But this will not fix the bug.
My /var/run/ nm-dns- dnsmasq. conf contained
server=10.1.0.4 195.202. 128.3
server=10.1.0.254
server=
wolf@mbp:~$ ps -elf | grep dnsmasq in-foreground --no-hosts --bind-interfaces --pid-file= /var/run/ sendsigs. omit.d/ network- manager. dnsmasq. pid --listen- address= 127.0.0. 1 --conf- file=/var/ run/nm- dns-dnsmasq. conf --cache-size=0 --proxy-dnssec
4 S nobody 25661 25624 0 80 0 - 7579 poll_s 15:20 ? 00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-
0 S wolf 25774 25489 0 80 0 - 2720 pipe_w 15:21 pts/1 00:00:00 grep --color=auto dnsmasq
wolf@mbp:~$
Thomas, please understand that I don't have the time to reiterate on situations that I have solved by reverting back to the original state. I gave you enough hints to solve the issue. You can set up a situation like mine in a bunch of virtual machines and simulate the effects.
I have a solution by disabling dnsmasq in network manager.
You might as well close this incident. But this will not fix the bug.