Issues with local resolves on v6

Help
1

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, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

On PiHole v5.8.x I was able to create a local DNS record example unifi that would resolve for 10.10.1.1 and resolve on both nslookup and the browser by navigating to the simple record https://unifi

Details relevant to your system/install:

  • Operating System - Ubuntu 24.04 LTS
  • Hardware - Intel Nuc i5 also tried on VM.
  • No Docker but installed using the automated installer

Actual Behaviour:

On Pihole v6 (clean install) it is not responding on the browser when navigating to https://unifi

I recovered the VM of my previous PiHole running v5.8.x and did not encountered the issue.
I also tried to clean the Google Chrome DNS, tried different browsers (Edge and Firefox) performed a DNS Flush on windows, tried doing this on a mac as well.

I have tried looking at other threads and tried multiple things in the config, the closest to what I am experiencing is this thread. I even wiped and reinstalled the OS and disabled the systemd-resolved with no luck.
I am able to resolve using nslookup which is good but I would love to resolve simple names in the browser.

Debug Token:

2

Run from the client that fails to access https://unifi, please share the output of:

nslookup pi.hole

nslookup unifi

nslookup flurry.com
3

Here's the responses

image
image379×457 7.16 KB

4

Have you had a chance to look at the debug file?
Should I reupload it?

5

Your nslookup results show that Pi-hole does answer requests for unifi correctly.

Your debug log shows that your router is distributing an additional IPv4 as DNS server:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 6 seconds)
   Scanning all your interfaces for DHCP servers and IPv6 routers
   
   * Received 300 bytes from 10.10.50.1 @ eno1
     DHCP options:
      Message type: DHCPOFFER (2)
      dns-server: 10.10.50.53
      dns-server: 10.10.50.54

Does 10.10.50.54 know how to resolve unifi?

When accessing https://unifi, (how) do the respective DNS requests register in Pi-hole's Query Log?
What's the exact error message in your browser?

And I'd have expected flurry.com to return a 0.0.0.0 reply.
If you rerun that nslookup, how do the respective DNS requests register in Pi-hole's Query Log?