If you recently changed your Unbound configuration and now you can’t access the Internet, you can verify Unbound is behaving properly by doing the following two things:

  1. Verify Unbound is actually running.
  2. Verify your configuration is actually running.

This was tested on a Raspberry Pi 3 running Unbound recursive DNS and Pi-hole.

Verify Unbound Is Running

First things first. Type the following to make sure Unbound is running:

sudo service unbound restart

error restart unbound service

Uh oh. We have a service failure.

Verify Unbound Configuration is Loading

Next up, type this command:


verify unbound.checkconf

There’s our problem! In this example, a period was added after the last octet. Ask me how I came up with this example. 🙂

Fix the Unbound Configuration Error

Type in this command to load an editor:

sudo nano /etc/unbound/unbound.conf.d/pi-hole.conf

When the configuration file is loaded, fix your happy little mistake that nearly brought your entire network down.

If you don’t use nano, that’s great. Use whichever editor suits you.


That’s it. Let me know what you found out with your setup in the comments below!

Pin It on Pinterest