In this article
Take these steps while installing the DNSFilter Relay to setup auto-start in Linux environments, such as Ubuntu. This step ensures the Relay always restarts with the virtual machine.
This setup is only required when running the standalone Linux binary. Hypervisor images run the DNS relay inside a pre-configured Docker container that’s set to auto-start by default.
- Download the relay binary and put it somewhere known. For the sake of example:
/etc/relay/relay-linux-amd64 - Create a file called
/etc/systemd/system/dnsfrelay.service - Add this block to the file:
[Unit]
Description=DNSFilter Relay Service
After=network.target
StartLimitIntervalSec=0
[Service]
Type=simple
Restart=always
RestartSec=1
User=root
ExecStart=/etc/relay/relay-linux-amd64
[Install]
WantedBy=multi-user.target -
Start the service:
systemctl start dnsfrelay - Set the service to start on boot:
systemctl enable dnsfrelay
The Relay will now start with the system.
Comments
4 comments
Do I need to do this if I'm running DNS Filter via the ESX VM image? I wouldn't think so.
Hi Mike S Great question! You’re correct—if you’re using a ESX VM image, you don’t need to follow these steps.
This setup is only required when running the standalone Linux binary. All of our hypervisor images, including the ESX VM, run the DNS relay inside a pre-configured Docker container that’s set to auto-start by default.
Hope this helps, and let us know if anything isn’t behaving as expected!
Thanks for confirming.
My colleague wanted to make sure the agents would automatically restart upon reboot. We went through a cycle of reboots without the service starting before getting the tests on the relay to work properly.
The issue was he had forgot to start the docker relays containers, so the test and resolution wasn't working.
No problem, Mike S ! Please reach out if anything else comes up!
Please sign in to leave a comment.