Moving feature request over to the upstream project.
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Importance: Undecided => Wishlist
** Changed in: netplan.io (Ubuntu)
Status: Triaged =>
Moving it over to the netplan.io project, as nplan is deprecated.
Also, I'm marking it as a "Wishlist" item, which could be considered to be
implemented as a new feature.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
St
On Tue, Sep 04, 2018 at 03:26:12PM -, Mark Rodgers wrote:
> Steve: Maybe my comment does not really belong here, I agree. I admit
> that I have not fully investigated the problem -- the problem in my case
> being that a configuration with static IP does not appear to set the DNS
> correctly, ei
Steve: Maybe my comment does not really belong here, I agree. I admit
that I have not fully investigated the problem -- the problem in my case
being that a configuration with static IP does not appear to set the DNS
correctly, either via netplan (and networkd) or via systemd's resolver.
A web searc
Mark, this bug is solely about the lack of support for top-level
declarations of DNS preferences in netplan. At most, the consequence is
that you must repeat yourself in the netplan config. That's suboptimal
and a bug we should fix, but I don't see any reason one should ever work
around it by mak
There seem to be a number of workarounds on the Web, and most of them
revolve around modifying either the netplan config file or the systemd
resolver config. None really worked for me -- usually, the resolver
configuration did not survive a reboot.
I found a very unclean (but effective) workaround
@cyphermox: Why should the user have to maintain nameservers in two
separate places? netplan should support this and I don't think it
belongs in systemd. Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Please don't do that.
resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf and
should remain that way -- this makes sure any changes on the network are
reflected "automatically" in the resolver's behavior, since you'd be
asking systemd-resolved rather than the libc resolver, and it al
This is a workaround for the issue:
sudo rm -f /etc/resolv.conf
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo reboot
# Known Issue
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Is there a workaround for this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698023
Title:
netplan does not allow a top-level 'nameservers' stanza
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nplan (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/1698023
Title:
netp
11 matches
Mail list logo
