You are not logged in.

#1 2025-03-04 21:49:00

asafgre
Member
Registered: 2024-10-07
Posts: 4

No hostnames resolution in LAN

My Arch is 6 month old, and  never had local name resolution.
e.g.

# ping mediabox
ping: mediabox: Name or service not known

I've tried to consult with https://wiki.archlinux.org/title/Systemd-resolved, and some AI; but I don't some all of it,
such as - what's the basic components of local name resolution.

Here's what I found so far:

1) I don't seem to have any firewall rules [not sure how to verify that]

[b]cat /etc/iptables/iptables.rules[/b]
# Empty iptables rule file
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT

2) i have these packages installed:

core/systemd-resolvconf
extra/libmicrodns
core/dnssec-anchors 20190629-4 [b][[/b]installed[b]][/b]
extra/avahi 1:0.8+r194+g3f79789-3 [b][[/b]installed[b]][/b]
extra/bind 9.20.6-1 [b][[/b]installed[b]][/b]
extra/c-ares 1.34.4-1 [b][[/b]installed[b]][/b]
extra/dnsmasq 2.90-2 [b][[/b]installed[b]][/b]
extra/kdnssd 6.11.0-1 (kf6) [b][[/b]installed[b]][/b]
extra/libmicrodns 0.2.0-2 [b][[/b]installed[b]][/b]
extra/nss-mdns 0.15.1-2 [b][[/b]installed[b]][/b]

3)  dnsmasq is installed, but its service always fails because port 53 is occupied by "domain":

[b]$ grep ' 53/' /etc/services[/b]
domain             53/tcp
domain             53/udp

4) contents of /etc/systemd/resolved.conf -- all lines are commented out.

directory  /etc/systemd/resolved.conf.d/ doesn't exist.

contents of /etc/nsswitch.conf:

hosts: mymachines mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] files myhostname dns
networks: files
protocols: files
services: files
ethers: files
rpc: files
netgroup: files

contents of /run/systemd/resolve/stub-resolv.conf:

nameserver 127.0.0.53
options edns0 trust-ad
search .

contents of /etc/resolv.conf

# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 8.8.4.4

5) nslookup seems to resolve only my own computer:

$ nmap -sn 192.168.45.*

(... found about 8 local IPs ...)

$ nslookup 192.168.45.91
;; communications error to 127.0.0.53#53: timed out
** server can't find 91.45.168.192.in-addr.arpa: NXDOMAIN
$ resolvectl query 192.168.45.91
192.168.45.91: resolve call failed: Name '91.45.168.192.in-addr.arpa' not found

Can someone help me set up local LAN name resolution?

Offline

#2 2025-03-05 07:33:38

-thc
Member
Registered: 2017-03-15
Posts: 853

Re: No hostnames resolution in LAN

Your packages and configurations are somewhat "all over the place".

What do you want to set up? mDNS / avahi (with the implicit ".local" TLD)? Your own local zone (with bind or unbound or dnsmasq)?

Offline

#3 2025-03-05 14:32:16

seth
Member
Registered: 2012-09-03
Posts: 62,873

Re: No hostnames resolution in LAN

And before you're doing any of this: if you're using some consumer-grade modemrouterdhcpswitch combo, does it maybe provide local DNS resolution as well?
Or why are you using public DNS servers?

nmap _gateway

Offline

Board footer

Powered by FluxBB