After playing around with Pi-Hole on a Pi Zero to see how it does, it lost connection after a power cycle so that I could move the device to a more permanent location.
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Sat 2019-11-02 02:48:20 GMT; 9min ago
Docs: man:systemd-sysv-generator(8)
Process: 1238 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCC
Nov 02 02:48:18 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 02 02:48:18 raspberrypi pihole-FTL[1238]: Not running
Nov 02 02:48:19 raspberrypi su[1267]: (to pihole) root on none
Nov 02 02:48:19 raspberrypi su[1267]: pam_unix(su:session): session opened for use
Nov 02 02:48:20 raspberrypi pihole-FTL[1238]: dnsmasq: failed to create listening
Nov 02 02:48:20 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
Something is interfering with pihole-FTL launching on port 53. Let's see what's running on ports used by Pi-Hole and associated DNS servers. Output of the following command from the Pi terminal?
You have unbound listening on port 53, and this is interfering with pihole-FTL. To work alongside Pi-Hole, unbound should be on a separate port. The Pi-Hole guide for unbound puts it on port 5353.