mDNS and the local DNS settings - something not working

[shykitten55]

The issue I am facing:

In the Local DNS/DNS records part I can enter/create entries so rather than typing the IP, I can enter a name.
Or: that is the idea.
It isn't working.

See screen shot:

arlec1 for instance.

This machine is set up as the DNS for my network and I am seeing weird things happening on the DNS side of things.

For the sake of keeping things as simple as possible: ALL is done on that machine.

So, I say: ping arlec1 and it just doesn't like me.

pi@BedPi:/etc/avahi $ ping arlec1
ping: arlec1: Name or service not known

Ok, so let's dig a bit more:

pi@BedPi:~ $ dig arlec1

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> arlec1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13331
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;arlec1.				IN	A

;; AUTHORITY SECTION:
.			263	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022102201 1800 900 604800 86400

;; Query time: 12 msec
;; SERVER: 9.9.9.10#53(9.9.9.10)
;; WHEN: Sun Oct 23 13:41:25 AEDT 2022
;; MSG SIZE  rcvd: 110

pi@BedPi:~ $

Not good.

pi@BedPi:~ $ dig @192.168.0.83 arlec1

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Raspbian <<>> @192.168.0.83 arlec1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18837
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;arlec1.				IN	A

;; ANSWER SECTION:
arlec1.			0	IN	A	192.168.0.23

;; Query time: 1 msec
;; SERVER: 192.168.0.83#53(192.168.0.83)
;; WHEN: Sun Oct 23 13:42:20 AEDT 2022
;; MSG SIZE  rcvd: 51

pi@BedPi:~ $ 

Better.

To digress for a moment to a Ubuntu machine I see this:

resolvectl status
Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (eno1)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.83
       DNS Servers: 192.168.0.83

Note the -mDNS

Does that mean this machine is NOT seeing a mDNS server broadcasting on this network?

(Back to the Pi)
After searching I hope I have all the right things set.
avahi-daemon is/was restarted after the edit.

pi@BedPi:/etc/avahi $ cat avahi-daemon.conf 
# This file is part of avahi.
#
# avahi is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2 of the
# License, or (at your option) any later version.
#
# avahi is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
# or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
# License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with avahi; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.

# See avahi-daemon.conf(5) for more information on this configuration
# file!

[server]
#host-name=foo
#domain-name=local
#browse-domains=0pointer.de, zeroconf.org
use-ipv4=yes
#use-ipv6=yes
allow-interfaces=eth0
#deny-interfaces=eth1
#check-response-ttl=no
#use-iff-running=no
#enable-dbus=yes
#disallow-other-stacks=no
#allow-point-to-point=no
#cache-entries-max=4096
#clients-max=4096
#objects-per-client-max=1024
#entries-per-entry-group-max=32
ratelimit-interval-usec=1000000
ratelimit-burst=1000

[wide-area]
enable-wide-area=yes

[publish]
#disable-publishing=no
#disable-user-service-publishing=no
#add-service-cookie=no
#publish-addresses=yes
publish-hinfo=no
#publish-workstation=no
publish-domain=yes
publish-dns-servers=192.168.0.83
#publish-dns-servers=192.168.50.1, 192.168.50.2
#publish-resolv-conf-dns-servers=yes
#publish-aaaa-on-ipv4=yes
#publish-a-on-ipv6=no

[reflector]
#enable-reflector=no
#reflect-ipv=no

[rlimits]
#rlimit-as=
#rlimit-core=0
#rlimit-data=8388608
#rlimit-fsize=0
#rlimit-nofile=768
#rlimit-stack=8388608
#rlimit-nproc=3
pi@BedPi:/etc/avahi $ 

Details about my system:

RasPi 2B Buster running PiHole.
PiHole 5.13
FTL 5.18.2
GUI 5.16

What I have changed since installing Pi-hole:

I am not sure I have CHANGED anything.

I am just not understanding why mDNS isn't working.

[jfb]

@shykitten55

SERVER: 9.9.9.10#53(9.9.9.10)

This client is using Quad9 for DNS, not Pi-hole.

[shykitten55]

Yes, and I can't argue there given what is shown.
Though: ;; SERVER: 9.9.9.10#53(9.9.9.10). What does the ;; at the start of the line mean?
And when I do the dig @192.168.0.83 I get

;; ANSWER SECTION:
arlec1.			0	IN	A	192.168.0.23

;; Query time: 1 msec
;; SERVER: 192.168.0.83#53(192.168.0.83)

And is shown in the ;;ANSWER SECTION: which isn't shown in the first one.

But... (drum roll) if I VNC to that machine and look at the GUI, I see this:

So the DNS is set to 192.168.0.83 on that machine (RasPi).

Which is only the start of the problem.

My main machine has the same problem:

If I try to dig arlec1 it gives me this:

dig arlec1

; <<>> DiG 9.16.8-Ubuntu <<>> arlec1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 48734
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;arlec1.				IN	A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Oct 23 16:28:20 AEDT 2022
;; MSG SIZE  rcvd: 35

Though this time the server is 127.0.0.53.
Well, I say that but the line starts with ;; So it that really true or not?
And there is no ANSWER SECTION so I'm guessing there is more here than I am seeing.

(Ok, update)

Looking at the Pi in /etc/dhcpcd.conf - the last bit:

interface eth0
static ip_address=192.168.0.83
static routers=192.168.0.254
static domain_name_servers=192.168.0.83
static domain_search=
static ip_address=192.168.0.83/24
static routers=192.168.0.254
static domain_name_servers=9.9.9.10 149.112.112.10

Ok, it says (a duplicate entry) for static domain_name_servers=
I've remarked that line and shall try again.

That seems to have fixed it.
Thanks.

Oh I've done a whois, but how did the 149.112.112.10 get put in my DNS list?
(Semi rhetorical)

[shykitten55]

Now in the bigger picture:

My Main machine. Ubuntu.
It seems to be suffering the same kind of problem.

Alas there is no /etc/dhcpcd.conf file.
There is a /etc/dhcp directory but it doesn't have a dhcpcd.conf file either.
It does have a dhclient.conf file which is not for what I am looking.

So now the problem has moved to the ubuntu machine.

[shykitten55]

Ok, I have got things sort of working.
I can now ping devices by name, but there is now a whole other problem.
(See new thread)

I don't understand what I did to get that working so sorry, I can't share it.