[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

2021-06-30 Thread Dan Streetman
please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

2019-09-29 Thread Dmitry Lapshin via ubuntu-bugs
Any progress here? systemd-resolved has plus that it's integrated with
DNS options from systemd-networkd, but for end user it has many issues,
especially related to DNSSEC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

2018-08-29 Thread Michel-Ekimia
We seem to hit the same problem here.

Can you post you NetworkManager.conf file ? if it was not upgraded
correctly that could be the issue

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

2018-07-19 Thread Jason Heeris
Note also that upstream claim that "resolved is not supposed to be a DNS
server"[1], so I'm a bit confused as to why Ubuntu is configured to pass
every DNS query through it. Do I need to reconfigure something?

  [1]
https://github.com/systemd/systemd/issues/4621#issuecomment-260050033

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782679/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs