The issue I am facing:
Using Local DNS
Details about my system:
Fedora Server 33 virtual machine. Non-DHCP
What I have changed since installing Pi-hole:
Installed unbound. Add local host to Local DNS Records
My apologies ahead of time for being lengthy...
Current LAN setup:
Router: Ubiquiti USG
Role: DHCP
Domain name: offworld.lan
Pi-Hole: Fedora Server 33 running as a virtual machine on a dedicated virtual host
Role: DNS server/Recursive with unbound
DNS settings:
Upstream DNS Servers: Default Google deselected with custom 127.0.0.1#5335, everything else default.
Local DNS Records:
enas 192.168.15.8
enas.offworld.lan 192.168.15.8
My path to attempting to get local DNS resolution working led me to a video on YouTube for installing and configuring unbound. Unbound is working. I stated that so that all will know that installing unbound is one of the biggest changes to my Pi-hole configuration.
Now, stating all that, I am trying to understand why resolving local DNS is inconsistent. I can resolve my client hostname with the FQDN but not just with its hostname. Why is that?
Below are results from one of my Fedora client machines looking at the Fedora server Pi-hole for DNS.
[ed@edfed: ~]$ dig enas
; <<>> DiG 9.16.20-RH <<>> enas
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 64155
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;enas. IN A
;; Query time: 3526 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Oct 07 06:59:08 EDT 2021
;; MSG SIZE rcvd: 33
[ed@edfed: ~]$ dig enas.offworld.lan
; <<>> DiG 9.16.20-RH <<>> enas.offworld.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 489
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;enas.offworld.lan. IN A
;; ANSWER SECTION:
enas.offworld.lan. 0 IN A 192.168.15.8
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Oct 07 06:59:39 EDT 2021
;; MSG SIZE rcvd: 62
ed@edfed: ~]$ ping enas
ping: enas: Name or service not known
[ed@edfed: ~]$ ping enas.offworld.lan
PING enas.offworld.lan (192.168.15.8) 56(84) bytes of data.
64 bytes from enas (192.168.15.8): icmp_seq=1 ttl=64 time=0.434 ms
64 bytes from enas (192.168.15.8): icmp_seq=2 ttl=64 time=0.227 ms
64 bytes from enas (192.168.15.8): icmp_seq=3 ttl=64 time=0.232 ms
^C
--- enas.offworld.lan ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.227/0.297/0.434/0.096 ms
I would love to be able to resolve clients on my LAN with just hostname to eliminate the additional typing of the FQDN.
Any assistance would be greatly appreciated.