Custom DNS entries not working

Help
1

Expected Behaviour:

i use .lan for local things and set up one entry for my pihole and one for my router.
i expect to be able to reach pihole under pihole.lan.
Raspbian GNU/Linux 11
Raspberry Pi 4 B

Actual Behaviour:

i can not reach my custom entries from any device on the network, and the pi.hole is only accesible from my android device. i have manually added the pi as the dns server in the adapter settings on my pc and on the android device the DNS is set correctly.

Debug Token:

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

2

Try configure solely the Pi-hole IP for DNS and no others:

3

image
the pi does DHCP in my network and as you can see the only DNS server my PC has is the PI.
the pi is the only dns server in my network

4

image
i have run nmap and this is what i got. the one additional device is my android device.
i have also enabled ipv6 in the DHCP of my raspberry and now i can reach pi.hole sometimes but not the other one
.

5

What/who is that 2a02:810b... IPv6 DNS server address?

Does it show up when run below on the Pi-hole host?
Dont post output for this one here as it might display your global public IP address if have one!

ip -br -6 a

6

no it does not, but the adress is not assigned to any of my devices (pc, phone, router, pi) so i am not sure why the pi would give this one out as the ipv6 adress for DNS

7

Its most likely the address being advertised from your router via IPv6 router advertisement or short RA.
You could try check below reverse lookup (IP to name):

dig @192.168.0.1 -x 2a02:810b:48c0:2824:10:18ff:feee:bdc

IPv6 RA needs to be configured in the router.
Check the router manual for this.
Or if not able to, you could opt to disable IPv6 support in the router settings for your LAN entirely.

8

the adress seems to be a dns server from my ISP

i can not disable ipv6 on my router (isp...) but even when i disable ipv6 in my adapter settings on windows i cant reach the custom entry. pi.hole seems to work on my pc now.

9

Use nslookup run on that client:

nslookup -type=a <DOMAIN_NAME> <DNS_SERVER_IP>

Eg 10.0.0.4 is my Pi-hole host and the name nas is my NAS (EDIT: with custom DNS record):

C:\>nslookup -type=a nas 10.0.0.4
Server:  pi.hole
Address:  10.0.0.4

Name:    nas.home.dehakkelaar.nl
Address:  10.0.0.3

At the same time check/tail the logs live with below:

pi@ph5b:~ $ pihole -t
[..]
Oct  2 13:01:52: query[A] nas.home.dehakkelaar.nl from 10.0.0.11
Oct  2 13:01:52: /etc/pihole/custom.list nas.home.dehakkelaar.nl is 10.0.0.3

And on that same client, run the nslookup without <DNS_SERVER_IP> to check if get same results eg:

nslookup -type=a <DOMAIN>

10

Client:
nslookup -type=a kablebox.lan 192.168.0.98
Server: 192.168.0.98
Address: 192.168.0.98#53

** server can't find kablebox.lan: NXDOMAIN

nslookup -type=a kabelbox.lan
Server: 172.20.144.1
Address: 172.20.144.1#53

Non-authoritative answer:
Name: kabelbox.lan
Address: 192.168.0.1

PIhole:

Oct 2 13:17:56: query[A] kablebox.lan from 192.168.0.139
Oct 2 13:17:56: config kablebox.lan is NXDOMAIN

Oct 2 13:27:16: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:27:16: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1

11

Could you post the full nslookup command that was used above? Thanks!

How does your custom DNS entry look like?

grep kablebox /etc/pihole/custom.list

Have you configured a Domain?

grep PIHOLE_DOMAIN= /etc/pihole/setupVars.conf

Does your Windows cllient have a .lan "DNS suffix":

ipconfig /all

12

i edited the other one before i read your last reply

grep kabelbox /etc/pihole/custom.list
192.168.0.1 kabelbox.lan

there is a line in ipconfig /all " Connection-specific DNS Suffix . : lan "

13

One is for:
kablebox.lan

The other is for:
kabelbox.lan

14

sorry i missed the typo now i get the same result

15

Lost in translation :wink:

16

i can reach the router by using the ip but not the custom adress
when i use the latter it just shows a white screen not a "website not reached" screen
same for my pihole.lan

17

Tail the logs live when trying to browse:

pihole -t

Reboot that client thats used for testing bc cache is everywhere!

18

Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[AAAA] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: config kabelbox.lan is NODATA-IPv6
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:49: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:44:49: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:44:50: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:50: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:50: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:50: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:50: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:50: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:50: query[AAAA] pihole.lan from 192.168.0.139
Oct 2 13:44:50: config pihole.lan is NODATA-IPv6
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98
Oct 2 13:44:51: query[A] pihole.lan from 192.168.0.139
Oct 2 13:44:51: /etc/pihole/custom.list pihole.lan is 192.168.0.98

19

That looks all good.
Do you run a virus killer?
Try disable that one and try again.

20

same result when all popup/ad blockers are disabled.
i also tried it in my untouched edge installation which gave me a website not reached response
logs from the edge attempt:
Oct 2 13:48:36: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:36: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:36: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:36: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:36: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:36: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:36: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:36: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:36: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:36: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:37: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:37: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:37: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:37: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1
Oct 2 13:48:37: query[A] kabelbox.lan from 192.168.0.139
Oct 2 13:48:37: /etc/pihole/custom.list kabelbox.lan is 192.168.0.1