ExternalVendorCode/devilbox
1
0
Fork 0
mirror of https://github.com/cytopia/devilbox.git synced 2024-12-25 23:41:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #256 from cytopia/doc-auto-dns

Browse Source 
Fix #225 systemd-resolvd documentation
This commit is contained in:
cytopia 2018-05-08 09:07:00 +02:00 committed by GitHub
commit 30a3246591
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 45 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
docs/configuration-global/auto-dns.rst
View File

@ -78,6 +78,12 @@ The output should look like this (It is only important that there is no ``:53``.
Linux Linux
----- -----
On Linux the DNS settings can be controlled by various different methods. Two of them are via
Network Manager and systemd-resolved. Choose on of the methods depending on your local setup.
Network Manager
^^^^^^^^^^^^^^^
If the prerequisites are met, you can edit ``/etc/dhcp/dhclient.conf`` with root or sudo privileges If the prerequisites are met, you can edit ``/etc/dhcp/dhclient.conf`` with root or sudo privileges
and add an instruction, which tells your local DHCP client that whenever any of your DNS servers and add an instruction, which tells your local DHCP client that whenever any of your DNS servers
are changed, you always want to have an additional entry, which is the one from the Devilbox. are changed, you always want to have an additional entry, which is the one from the Devilbox.
@ -95,10 +101,10 @@ When you do that for the first time, you need to restart the ``network-manager``
.. code-block:: bash .. code-block:: bash
# Via service command # Via service command
$ sudo service network-manager restart host> sudo service network-manager restart
# Or the systemd way # Or the systemd way
$ sudo systemctl restart network-manager host> sudo systemctl restart network-manager
This will make sure that whenever your /etc/resolv.conf is deployed, you will have ``127.0.0.1`` This will make sure that whenever your /etc/resolv.conf is deployed, you will have ``127.0.0.1``
as the first entry and also make use of any other DNS server which are deployed via the LAN's DHCP server. as the first entry and also make use of any other DNS server which are deployed via the LAN's DHCP server.
@ -107,6 +113,43 @@ If the Devilbox DNS server is not running, it does not affect the name resolutio
still have other entries in ``/etc/resolv.conf``. still have other entries in ``/etc/resolv.conf``.
systemd-resolved
^^^^^^^^^^^^^^^^
In case you are using systemd-resolved instead of NetworkManager, add the following line to
the very beginning to ``/etc/resolv.conf.head``:
.. code-block:: bash
:caption: /etc/resolv.conf.head
:name: /etc/resolv.conf.head
nameserver 127.0.0.1
Prevent NetworkManager from modifying ``/etc/resolv.conf`` and leave everything to
systemd-resolved by adding the following line under the ``[main]`` section of
``/etc/NetworkManager/NetworkManager.conf``
.. code-block:: bash
:caption: /etc/NetworkManager/NetworkManager.conf
:name: /etc/NetworkManager/NetworkManager.conf
dns=none
As a last step you will have to restart ``systemd-resolved``.
.. code-block:: bash
host> sudo systemctl stop systemd-resolved
host> sudo systemctl start systemd-resolved
Once done, you can verify if the new DNS settings are effective:
.. code-block:: bash
host> systemd-resolve --status
.. seealso:: `Archlinux Wiki: resolv.conf <https://wiki.archlinux.org/index.php/Resolv.conf#Modify_the_dhcpcd_config>`_
MacOS MacOS
----- -----