Pihole own DNS entry coming from Blacklist

Expected Behaviour:

Pihole device announces it's DNS name as that set in the "pi-hole hostname" box on the settings page.

Actual Behaviour:

Pihole is announcing its DNS name (as checked via nslookup and ping -a [IPADDRESS]) as the first entry in the Exact blacklist. I.E. If blacklist is blank, and a client runs ipconfig /flushdns followed by nslookup it shows the DNS server to be called whatever's in the hostname box on the settings page. If an entry is made to the exact blacklist, and ipconfig /flushdns followed by nslookup are run on the client again, the DNS server's name is that entry on the blacklist.

Debug Token:

Unnecessary I feel, but can be supplied.

Thanks for your report. This comes from a dnsmasq bug and has already been fixed in the current development version of Pi-hole.

Please change your /etc/dnsmasq.d/01-pihole.conf from

addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/local.list
addn-hosts=/etc/pihole/black.list

to

addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list

i.e. make local.list the last of the three entries in that file.

See also

Thanks for that - sorted. So the bug is in dnsmasq, and changing the list load order masks the effect of the bug?

Exactly. Is it now correct for you?