MDNS: Difference between revisions
m (Use lowercase first letter in display of article title.) |
No edit summary |
||
Line 33: | Line 33: | ||
Enable and start avahi2dns with | Enable and start avahi2dns with | ||
{{cmd|doas rc-update add | {{cmd|doas rc-update add avahi2dns | ||
doas rc-service | doas rc-service avahi2dns start}} | ||
It should now be possible to use DNS to query the address of the printer. | It should now be possible to use DNS to query the address of the printer. |
Revision as of 10:22, 3 May 2024
Multicast DNS is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.
Setup avahi
Install, enable and start avahi with:
doas apk add avahi doas rc-update add avahi-daemon doas rc-service avahi-daemon start
It should now be possible to browse results. To look for a printer, use:
doas apk add avahi-tools avahi-browse --resolve --terminate _ipp._tcp
Make note of the hostname, as we will use it afterwards.
Setup avahi2dns
Name resolution is implemented by musl, and it only supports DNS, so we have to map the avahi results to a regular DNS server. This is done by avahi2dns.
git clone https://github.com/LouisBrunner/avahi2dns cd avahi2dns go build doas cp avahi2dns /usr/bin doas cp openrc/avahi2dns /etc/init.d
since we will want a full DNS server running at port 53, we need to configure avahi2dns to use another port. Do that by creating /etc/conf.d/avahi2dns containing:
command_args="-p 5354"
Enable and start avahi2dns with
doas rc-update add avahi2dns doas rc-service avahi2dns start
It should now be possible to use DNS to query the address of the printer.
drill -p 5354 @127.0.0.1 <printer_name>.local
Where printer_name is the hostname given by avahi-browse.
Setup DNS resolver
We now need to setup a DNS resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the DHCP provided server for the regular DNS requests. We will use unbound as the server and resolvconf to inform unbound about the DHCP results.
Install the programs:
doas apk add openresolv unbound
Create /etc/resolvconf.conf:
name_servers=127.0.0.1 unbound_conf=/etc/unbound-resolvconf.conf
This tells resolveconf to use a local nameserver and pass the DHCP provided DNS server to unbound
Create /etc/unbound/unbound.conf:
forward-zone: name: "local" forward-addr: 127.0.0.1@5354 include: "/etc/unbound-resolvconf.conf" server: do-not-query-localhost: no domain-insecure: "local"
This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.
Enable and start unbound
doas rc-update add unbound doas rc-service unbound start
Setup DHCP client
How send the DHCP provided DNS to resolvconf depends on the DHCP client being used.
udhcpc
This is the DHCP client in busybox, and will work for both wired and wireless interfaces.
Create /etc/udhcpc/udhcpc.conf:
RESOLV_CONF="/etc/udhcpc-resolv.conf"
Create /etc/udhcpc/post-bound/resolvconf:
#!/bin/sh cat /etc/udhcpc-resolv.conf | resolvconf -a $interface
An inconvenience of this setup is that udhcpc will not reconfigure the interface when connecting to other wifi networks. For that to happen one has to run
iwctl station wlan0 connect <network_name> doas kill -USR2 $(cat /run/udhcpc.wlan0.pid) doas kill -USR1 $(cat /run/udhcpc.wlan0.pid)
iwd
To avoid having to manually reconfigure the wifi interface, we can configure iwd to use DHCP internally and forward DNS server info to resolveconf. To do that create /etc/iwd/main.conf:
[General] EnableNetworkConfiguration=True
[Network] NameResolvingService=resolvconf
Test the setup
You should now be able to query for both the printer address and regular addresses with
drill @127.0.0.1 <printer_name>.local drill @127.0.0.1 alpinelinux.org
Your /etc/resolv.conf should also contain
nameserver 127.0.0.1
Printer discovery should now be working.