Skip to content

Commit

Permalink
Seems to have found the winning combination of restarts. Removed sudo…
Browse files Browse the repository at this point in the history
… as asked.
  • Loading branch information
user committed Dec 8, 2024
1 parent 6f37cb8 commit 50cc98f
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions doc/howto/network_bridge_resolved.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,15 +96,16 @@ Domains=~lxd

If you have NOT freshly installed `lxd` (you've rebooted since install), then you only need to reload `systemd-resolved`:

sudo systemctl restart systemd-resolved.service
systemctl restart systemd-resolved.service

In case you **haven't rebooted yet since first initializing `lxd`**, then you need to restart `lxd` first or just reboot (see https://github.com/canonical/lxd/issues/14588):
In case you **haven't rebooted yet since first initializing `lxd`**, then you need to either A) reboot the system, or B) reload `systemd-networkd` (to reload the `.network` files) and restart `lxd` (to add the routing).

networkctl reload
snap restart lxd

You can test that the configuration got applied by running:

sudo resolvectl status
resolvectl status

The output should contain a part similar to this (you can see the DNS server and the `.lxd` domain mentioned):

Expand Down

0 comments on commit 50cc98f

Please sign in to comment.