[Desktop-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more
however, when I check: systemd-resolve --status I get this: Global172,in-addr. DNS DOmain: dhcp.inet.fi DNSSEC NTA: 10.in-add.arpa 16.172.in-addr.arpa 168.192.in-add.arpa . . . . Link 3 (WLP4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes DNS Servers: 192.168.55.5 DNS Domain: Speedport_W_724..[some Number from my Router/Modemmodel] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Fix Released Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more
This is not working in ubuntu gnome: network-manager 1.4.4-1ubuntu3 network-manager-gnome 1.4.2-1ubuntu4 in /var/log/syslog I get lots of Error Messages after nm-dispatcher: req:3 'up' [wlp4s0]: start running ordered scripts... systemd-resolved[1104]: Switching to DNS server 192.168.55.5 for interface wlp4s0 systemd-resolved[1104]: DNSSEC validation failed for question . IN SOA: no-signature systemd-resolved[1104]: DNSSEC validation failed for question com IN DS: no-signature systemd-resolved[1104]: DNSSEC validation failed for question com IN SOA: no-signature systemd-resolved[1104]: DNSSEC validation failed for question com IN DNSKEY: no-signature systemd-resolved[1104]: DNSSEC validation failed for question ubuntu.com IN DS: no-signature systemd-resolved[1104]: DNSSEC validation failed for question ubuntu.com IN SOA: no-signature systemd-resolved[1104]: DNSSEC validation failed for question daisy.ubuntu.com IN DS: no-signature systemd-resolved[1104]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: no-signature systemd-resolved[1104]: DNSSEC validation failed for question .. this basically fills up my syslog whenever I use anything with networking it clearly is a problem with the DNS as I can reach my hosts, when I just use the IP Adresses such as http://46.4.95.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647133 Title: dns=dnsmasq does not work any more Status in network-manager package in Ubuntu: Fix Released Bug description: Network-manager will make my network connection immediately lost after updating to the newest version 1.4.2-2ubuntu4. However, downgrading to the previous version 1.4.2-2ubuntu3 the network connection is back again and fine. If, with this version, I remove the file (link) /etc/resolv.conf the network is broken again. Rebooting solves this, as network-manager creates a new resolv.conf file. The newest version 1.4.2-2ubuntu4 also creates the very same kind of file, but no network. I have the latest (Gnome-shell DE) updates installed and of course all packages that network-manager depends on. But not the ones it only recommends or suggests. Should I have resolvconf installed? I think not, as isc-dhcp-client only suggests it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp