lokinet
/
lokinet
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0fe716e1dd'
${ noResults }
lokinet/contrib/systemd-resolved
History
Jason Rhinelander 4ef25ef679
Add systemd-resolved dynamic DNS updating 		2 years ago
..
README.md Add systemd-resolved dynamic DNS updating 2 years ago
lokinet.pkla Add systemd-resolved dynamic DNS updating 2 years ago
lokinet.rules Add systemd-resolved dynamic DNS updating 2 years ago

README.md

Lokinet now talks to systemd directly via sdbus to set up DNS, but in order for this to work the user running lokinet (assumed _lokinet in these example files) needs permission to set dns servers and domains.

To set up the permissions:

  • If lokinet is running as some user other than _lokinet the change the _lokinet username inside lokinet.rules and lokinet.pkla.

  • If on a Debian or Debian-derived distribution (such as Ubuntu) using polkit 105, copy lokinet.pkla to /var/lib/polkit-1/localauthority/10-vendor.d/lokinet.pkla (for a distro install) or /etc/polkit-1/localauthority.conf.d/ (for a local install).

  • Copy lokinet.rules to /usr/share/polkit-1/rules.d/ (distro install) or /etc/polkit-1/rules.d (local install).

Make use of it by switching to systemd-resolved:

sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
sudo systemctl enable --now systemd-resolved