Using redundant Upstream DNS servers w/Cloudflared = Lost Connection to API

#22

This should be possible but I haven’t tried it myself for a few years so I’m not sure if it still works as expected (it should, though).

Create a file /etc/dnsmasq.d/99-custom.conf and put there:

strict-order

/etc/resolv.conf should still only be:

nameserver 127.0.0.1

Then ensure that the servers are in the correct order in /etc/dnsmasq.d/01-pihole.conf (first listed = first asked) and run

pihole restartdns

However, I haven’t found it necessary to define a fallback solution for Unbound which is working 100% perfect for me since years in a mid-business sizes environment.

2 Likes

"strict-order" seems to be working in reverse
#23

Thank you for this.

I am now using Unbound with multiple upstream servers over TLS and a fallback to its recursive functionality. Seems to be working perfectly.

0 Likes

closed #24

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

0 Likes