Must select a 2nd DNS to browse websites

[gil80]

The issue I am facing:
Cannot browse websites if I don't add a 2nd DNS entry in Pihole DNS settings.

Details about my system:
Running latest pihole on RPi.

What I have changed since installing Pi-hole:
Just updated to the latest version.

Here is the diag file: https://tricorder.pi-hole.net/ueUzk7fu/

If I disable a selection of DNS, then I cannot browse, (I get Hmmm… can't reach this page
www.google.com’s server IP address could not be found.) which was not an issue in the past because I use Unbound as my DNS on 127.0.0.1#53

Now, in order to browse websites, I must select a DNS in the DNS list.

Why was it changed?

[rdwebdesign]

@gil80

I use Unbound as my DNS on 127.0.0.1#53

No. This is not unbound.

Pi-hole is using this port:

...
[✓] udp:0.0.0.0:53 is in use by pihole-FTL
...
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL

127.0.0.1 is the loopback address (an internal IP address that sends data back to the local system).
The result is: you are saying to Pi-hole to use itself as upstream.

Unbound is using a different port (5335):

    udp:127.0.0.1:5335 is in use by unbound

Change the address to use the correct port.

[gil80]

Ok, thank you.
I updated the DNS port as you described.

Seem ok now, but I got this error today:
Connection error (**127.0.0.1#5335** ): TCP connection failed while receiving payload length from upstream (**Connection prematurely closed by remote server** )

[rdwebdesign]

@gil80

Seem ok now, but I got this error today:
Connection error (**127.0.0.1#5335** ): TCP connection failed while receiving payload length from upstream (**Connection prematurely closed by remote server** )

This is harmless.

This error is just saying Pi-hole sent a query to Unbound, waited for a response, Unbound never answers the query back to Pi-hole and closes the connection.

This is an Unbound issue (already reported to unbound).

There is nothing Pi-hole can do about it. There is nothing you can do about it, unless unbound releases a fix.

You can read more about this issue here:

• UDP Error - #47 by Bucking_Horn (second paragraph and below);
• Two Pi-hole instances, One with "failed to send..." - #44 by DL6ER

[gil80]

Thank you for your help!