mirror of
https://github.com/optim-enterprises-bv/secureblue.git
synced 2025-11-03 03:48:22 +00:00
docs: add note about VM network connectivity
This commit is contained in:
4
FAQ.md
4
FAQ.md
@@ -68,3 +68,7 @@ If you still want to enable this functionality, run `ujust toggle-ghns`
|
|||||||
If your system time is off by an excessive amount due to rare conditions like a CMOS reset, your network will not connect. A one-time manual reset will fix this. This should never be required except under very rare circumstances.
|
If your system time is off by an excessive amount due to rare conditions like a CMOS reset, your network will not connect. A one-time manual reset will fix this. This should never be required except under very rare circumstances.
|
||||||
|
|
||||||
For more technical detail, see [#268](https://github.com/secureblue/secureblue/issues/268)
|
For more technical detail, see [#268](https://github.com/secureblue/secureblue/issues/268)
|
||||||
|
|
||||||
|
#### Why is DNS broken on my secureblue VM?
|
||||||
|
|
||||||
|
The DNSSEC setting we set in `/etc/systemd/resolved.conf.d/securedns.conf` causes known issues with network connectivity when secureblue is used in a VM. To fix it, comment out `DNSSEC=allow-downgrade` in that file and manually set a dns provider in network settings.
|
||||||
|
|||||||
Reference in New Issue
Block a user