Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
[ Website https://nzb.su should be accessible from the web. Site is not blacklisted.]
Actual Behaviour:
_[ Website https://nzb.su is no longer accessible. I keep getting the following error when attempting to access the website "ERR_NAME_NOT_RESOLVED" while pihole is enabled or disabled. I had this issue in Pihole v4 and was hoping it would be corrected with Pihole v5, but it is still happening. So I did a fresh install of Pihole v5 and the site was accessible with the default blocklists. After installing Unbound it stops working and seems that it may be the culprit. After the Unbound install and trying to access the site the next day it is returning the "ERR_NAME_NOT_RESOLVED." Anyway to help resolve this issue? Or will I have to not use Unbound as my blocking solution? I have left 2 debug tokens as I am running 2 piholes with unbound. I'm not sure if this is resulting to my issue as well. Both piholes have unbound with the default blocklists only.
So I decided to start from scratch as I had originally upgraded from pihole v4 to pihole v5. Wiped my card and did a fresh install of pihole v5. Everything worked fine with the default setup for accessing the website. It wasn't until I installed unbound that the site became inaccessible again. So I uninstalled unbound and it worked again as needed. So it seems that accessing the site while unbound is installed is either having a delay or timeout when attempting to access or unbound is blocking it entirely. I'm not sure if this is the correct assumption or if this is making any sense, but is there a way around this? Can I whitelist this site/domain somehow via unbound so that it is accessible?
If nzb.su's IP address would be fairly static, you could create a Custom DNS record for it in Pi-hole.
Of course, that would have to be updated manually once the IP address changed, and you may find that you also have to define additional records for any additional non-resolving subdomains that are used by the website itself.
Thanks for the help Bucking_Horn! I read up on the topic you mentioned and am following it as well, very similar. I will give this a try. Just to confirm that I am doing this correctly, as I have never added a custom DNS record before, under "Local DNS Records" in the left navigation I will be adding "https://nzb.su" as the domain and then "IP Address of nzb.su" in the IP Address field, correct?
Almost - no need to prefix a protocol, i.e. use the domain name nzb.su only.
Note that this is a somewhat dirty work-around only.
Even if it fixes the situation for you, you should stick with it only temporarily.
Since public IP addresses are involved, you'd now run the risk of ownership of that IP changing unnoticed, potentially to some malevolent entity. While public DNS servers would take care of that shift by updating the new address for nzb.su, you would continue to use that old IP address.
You should check whether that IP is still correct from time to time.
If this issue persists and the domain is important to you, I'd consider shelving unbound and use a conventional upstream DNS until this is solved.
