Archy's Blog

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0

Recently I've deployed a few raspberry pi nodes running raspbian and I did not want to have local users (except the 'pi' one) but have it using ldap for authentication. So here is what I did to get it working with raspbian 9. You'll have to start by installing the necessary package in this case, which is libnss-ldapd. [archy@rpi3 ~]$ sudo apt-get -y install libnss-ldapd When the installation is complete, we'll need to edit the config. Edit the /etc/nslcd.conf in your favorite editor [archy@rpi3 ~]$ sudo vim /etc/nslcd.conf uid nslcd # The user which nslcd will run as gid nslcd # The group which nslcd will run as uri ldap://ipa01.archyslife.lan # My ldap-servers which are queried uri ldap://ipa02.archyslife.lan # for authentication requests, base dc=archyslife,dc=lan # This base will be used for all queries. Next up is the name service switch file where we'll need to add a few things. Open up the file in your favorite editor an