New Setup Issues

Help
1

Hi everyone.

So I am installing pihole on a new machine (Ubuntu Server 20.04.03 amd64(x86_64))

First thing to notice

Expected a smooth install running
wget -O basic-install.sh https://install.pi-hole.net sudo bash basic-install.sh
but I got an error "Retrieval of supported OS list failed. dig failed with return code 9"
so I checked TXT records and list of supported OS and those were fine.
https://www.gdnspc.com/dns-propagation-checker/public-ipv4.html#TXT&versions.pi-hole.net
https://docs.pi-hole.net/main/prerequisites/

In this thread https://discourse.pi-hole.net/t/brand-new-to-raspberry-pi-and-pi-hole-need-help/41211 I found the command dig +short -t txt versions.pi-hole.net @ns1.pi-hole.net and when I ran it, it responded with ;; connection timed out; no servers could be reached. I changed the command to dig +short -t txt versions.pi-hole.net ns1.pi-hole.net and the response was: "Raspbian=9,10,11 Ubuntu=16,18,20,21 Debian=9,10,11 Fedora=32,33 CentOS=7,8".
To fix the setup I changed line 179 to cmdResult="$(dig +short -t txt "${remote_os_domain}" ns1.pi-hole.net 2>&1; echo $?)" and the setup was successful.

Second thing to notice

The second thing I found strange and couldn't get to work is Conditional Forwarding which I have used on previous versions.
I setup my values in Settings/DNS and all dns request timed out. On log I can see that the requests are forwarded to the specified DNS Server, but the reply is N/A.
Also what I found really strange is that this command dig +short -t txt versions.pi-hole.net ns1.pi-hole.net fails and in pihole logs shows reply N/A (this is forwarded to google servers)

Debug Token:

I cant upload token because of this error * Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net. Other hosts can resolve ricorder.pi-hole.net using pihole as dns server, but pihole server itself cant resolve it.

TIA

2

This means you blocked outgoing DNS queries over port 53 to ns1.pi-hole.net. Removing the @ makes your device use your locally configured resolver instead of ns1.pi-hole.net.

There is a bug in FTL's dnsmasq core that has been addressed already. Please have a look here to see how to work around

1 Like
3

Thanks for quick reply.
You were right on the first. My antivirus firewall was blocking DNS Request to ns1.pi-hole.net.
For the second, I did checkout the fix on conditional forwarding and now it is running fine.

4

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