[Freedombox-discuss] FreedomBox testing not resolving names from inside.

A. F. Cano afc54 at comcast.net
Fri Oct 6 21:52:13 BST 2023


APU2 as a test system, running FreedomBox testing, up to date as of a
few minutes ago.  One computer connected to one of the 2 inside

BIND app is disabled.  Dnsmasq is running on that interface.
(if I enable the GIND app, dnsmasq doesn't run and thus any connected
computer won't get any DNCP info.  The only way to connect then is to
manually configure the interface to the proper subnet the FreedomBox is
listening to, so the packets reach the FreedomBox.  Essentially
configuring the interface blind.)

/etc/resolv.conf on the connected computer ( says:

Unsurprisingly, dig www.debian.org says:

;; communications error to host unreachable
;; communications error to timed out
;; communications error to host unreachable

; <<>> DiG 9.18.19-1-deb12-u1-Debian <<>> www.debian.org
;; global options: +cmd
;; no servers could be reached

If I manually change /etc/resolv.conf and put in the name server that
the WAN interface found by using its own DHCP query, everything works.

Shouldn't the FreedomBox route the queries to resolve anything to the
nameserver/resolver to which it is connected via the WAN interface?

Is the nameserver that the connected computer is told (
correct? If so, the Freedombox should route the queries to the WAN
interface and its configured name server (/etc/resolv.conf on the
FreedomBox itself shows that one).

Alternatively, if dnsmasq told the connected computer that IP address
it would also work.

How should this work?



More information about the Freedombox-discuss mailing list