I can't access the admin page of Pi-hole using the dns name

[WeekendSuperhero]

I'm unable to access the admin page in pinhole

Expected Behavior:

I should be able to access my pi via http://pi.hole or http://pi.hole/admin

Actual Behaviour:

instead its says that it can't access the the page

Debug Token:

https://tricorder.pi-hole.net/pxud6zklvs

[PromoFaux]

DNS Resolution is working on your Pi-hole, per your debug log:

   [2020-05-14 12:47:22.351 8991]  -> Total DNS queries: 53344
   [2020-05-14 12:47:22.351 8991]  -> Cached DNS queries: 18989
   [2020-05-14 12:47:22.351 8991]  -> Forwarded DNS queries: 24155
   [2020-05-14 12:47:22.351 8991]  -> Blocked DNS queries: 10163
   [2020-05-14 12:47:22.351 8991]  -> Unknown DNS queries: 37
   [2020-05-14 12:47:22.351 8991]  -> Unique domains: 2535
   [2020-05-14 12:47:22.351 8991]  -> Unique clients: 59
   [2020-05-14 12:47:22.351 8991]  -> Known forward destinations: 4

On the client that you are trying to access the admin page from, what is the result of the following command?

nslookup pi.hole

[WeekendSuperhero]

Server:		2001:558:feed::1
Address:	2001:558:feed::1#53

** server can't find pi.hole: NXDOMAIN

[PromoFaux]

@WeekendSuperhero

Server: 2001:558:feed::1

So that client is using an IPv6 address to do DNS lookups. Though I am not sure where it comes from, as it doesn't match what is in your debug log. But then, I'm useless with V6 @DanSchaper could you have a quick look at this please?

@WeekendSuperhero
If you force a V4 lookup through your Pi-hole device, what do you get? i.e:

nslookup pi.hole 172.21.127.1

[WeekendSuperhero]

pi@raspberrypi:~ $ nslookup pi.hole 172.21.127.1
Server:		172.21.127.1
Address:	172.21.127.1#53

** server can't find pi.hole: NXDOMAIN

[PromoFaux]

That's very odd. Pi-hole is clearly working because you have 59 clients able to communicate with it.

Where are you running the nslookup commands? On the same device as Pi-hole or another one?

Are you able to access the web admin from other devices on your network?

[WeekendSuperhero]

@PromoFaux

nslookup pi.hole 172.21.127.1

but I get the same thing on the client that isn't the DNS server

% nslookup pi.hole 172.21.127.1
Server:		172.21.127.1
Address:	172.21.127.1#53

** server can't find pi.hole: NXDOMAIN

[PromoFaux]

@PromoFaux

172.21.127.1

Before we go too far, that is the IP address of your pihole, yes?

[PromoFaux]

Hold up:

*** [ DIAGNOSING ]: contents of /etc/pihole

-rw-r--r-- 1 root root 144 May 14 12:47 /etc/pihole/local.list
   172.21.127.68 raspberrypi
   2601:646:400:1060:aff9:a52f:2514:49b4 raspberrypi
   172.21.127.68 pi.hole
   2601:646:400:1060:aff9:a52f:2514:49b4 pi.hole

[WeekendSuperhero]

No, that isn't my pi hole address

[WeekendSuperhero]

now we are getting some where

Chromie@Anthracite ~ % nslookup pi.hole 172.21.127.68
Server:		172.21.127.68
Address:	172.21.127.68#53

Name:	pi.hole
Address: 172.21.127.68

Chromie@Anthracite ~ %```

[PromoFaux]

Sorry, yeah I misread the debug log.

Looks like your IPV6 address has changed since you first installed pi-hole.. the one in /etc/pihole/setupVars.conf is different to the actual IPV6.

If Pi-hole is handing out the one in setupVars.conf to your clients, then they're going to have a bad time resolving domains...

Please see this thread for some information about that:

Use IPv6 ULA addresses for Pi-hole

Many users have reported that frequently changing IPv6 addresses cause page load to be slow or even prevent from working at all. The issues can be fixed by updating the IPv6 address in /etc/pihole/setupVars.conf followed by a run of pihole -g. However, this solution turns out to be very inconvenient since it might be necessary to change the IPv6 address on a regular basis (maybe even multiple times a day). An alternative approach we are currently looking into is the usage of ULA addresses which…

[WeekendSuperhero]

I looked through there but the command pasted in the beginning doesn't seem to work i'm assuming there might need to be matching for fe as well ?