DNS resolution is currently unavailable Waiting until DNS resolution is available.........
Debug Token:
I can't upload the Token. I get this error:
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
[✗] There was an error uploading your debug log.
Please try again or contact the Pi-hole team for assistance.
A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
Other devices in your tailnet can reach this device at raspberrypi.xxx-xxxxxx.ts.net.
Resolvers (in preference order):
100.101.xxx.xx
Split DNS Routes:
ts.net. -> 199.xxx.xxx.xx
ts.net. -> 2620:111:8007::xx
Search Domains:
xxx-xxxxxx.ts.net
=== System DNS configuration ===
This is the DNS configuration that Tailscale believes your operating system is using.
Tailscale may use this configuration if 'Override Local DNS' is disabled in the admin console,
or if no resolvers are provided by the coordination server.
Nameservers:
192.168.1.1
2600:4040:2869:d500::1
Search domains:
mynetworksettings.com
[this is a preliminary version of this command; the output format may change in the future]
Your Issue occurs because pihole is using itself as dns-server.
During an update pihole is often temporarily unable to resolve dns.
You should configure your pihole to use an upstream dns-server for its own queries( or any server not being itself).
If you want filtering / analytic for the pihole machine itself I recommend having a /etc/resolv.conf similar to me:
nameserver 127.0.0.1
nameserver 1.1.1.1
For this you need to disable other services overriding /etc/resolv.conf
To avoid tailscale changing the dns-server run sudo tailscale set --accept-dns=false
You may need to set your networking service to ignore dns from dhcp.
For the update you can just edit /etc/resolv.conf, just note that tailscale(unless disabled) or your networking service( like networkmanager) may override that file on boot.