Cannot get custom DNS to unbound to stick in setupvars.conf

Please follow the below template, it will help us to help you!

Expected Behaviour:

If I set the custom DNS address 1 as 127.0.0.1#5353 it should stick, but it is not.

Actual Behaviour:

After I make the change in setupvars.conf, and then run pihole -r, DNS 1 reverts to 1.1.1.1

Debug Token:

2byghi3fiw

I installed unbound and am trying to use it as a recursive DNS resolver. I had difficulty (as noted on other posts and pages) assigning Custom 1 (IPv4) in the admin web page for this PiHole. I made the change in "setupVars.conf" to the following:

      PIHOLE_DNS_1=127.0.0.1#5353

When I restart PiHole (pihole -r), this reverts to 1.1.1.1 in the setupVars.conf file. The PiHole continues to operate, but it's not clear that it's using the unbound resolver.

In the admin console, when I tail the pihole.log, I see that DNS requests are being routed to 1.1.1.1.

What am I missing here? From the command line tests I have run, it seems that unbound is working properly, but PiHole is not routing it's DNS requests to unbound via the 127.0.0.1#5353 address.

Thanks in advance.

i'm new to PiHole and haven't programmed in about 30 years, so be gentle with me.

Are you running FTLDS?

I am not. I did a standard install of PiHole from the bash script. Then I separately installed unbound.

Pi-hole Version v3.3.1 Web Interface Version v3.3 FTL Version v3.0

Only the beta version of FTLDNS works with custom DNS ports.

The version you are on doesn’t.

If you want to try the beta version of FTLDNS, use these instructions:

https://discourse.pi-hole.net/t/help-us-beta-test-ftldns/

Also use this guid to properly pair unbound and Pi-hole FTLDNS:
https://docs.pi-hole.net/guides/unbound/

2 Likes

Thanks. I'll install that.

That was an easy install. FTLDNS is up and running and the DNS traffic is properly routing to unbound. Thanks for the help. Problem solved.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.