NSA325 - DNS problem after update to Debian 12

I updated my NSA325 to Debian 12 and lost network connection. The nas is connected on the lan, but no wan connection.

cat /etc/issue

Debian GNU/Linux 12 \n \l

Debian GNU/Linux 12 \n \l

cat: /etc/resolv.conf: No such file or directory

cat /etc/netconfig

#
# The network configuration file. This file is currently only used in
# conjunction with the TI-RPC code in the libtirpc library.
#
# Entries consist of:
#
#       <network_id> <semantics> <flags> <protofamily> <protoname> \
#               <device> <nametoaddr_libs>
#
# The <device> and <nametoaddr_libs> fields are always empty in this
# implementation.
#
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -
unix       tpi_cots_ord  -     loopback  -      -       -
root@debian:~# cat /etc/networks
default         0.0.0.0
loopback        127.0.0.0
link-local      169.254.0.0

I don't recognise the 169.254.x.x in the link-local

cat /etc/network/interfaces

rename /end0=eth0

auto lo eth0
iface lo inet loopback
# primary network interface
auto eth0
iface eth0 inet static
 address 192.168.2.21
 netmask 255.255.255.0
 gateway 192.168.2.1
 dns-nameservers  8.8.8.8 8.8.4.4 1.1.1.1

Edited 1 time(s). Last edit at 09/03/2025 10:42AM by Bobby.

Bobby,

Quote

I don't recognise the 169.254.x.x in the link-local

The IP 169.254.x.x sounds familiar, i.e. like a placeholder. I would not worry about it.

Do this to set the name server

echo "nameserver 192.168.2.1" > /etc/resolv.conf

or

echo "nameserver 8.8.8.8" > /etc/resolv.conf

And then test

ping 8.8.8.8
ping google.com

If it did not work, bring the network down and up. Try again.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

# echo "nameserver 192.168.2.1" > /etc/resolv.conf

-bash: /etc/resolv.conf: No such file or directory

~# ls -al /etc/resolv*
lrwxrwxrwx 1 root root   39 Jul 23  2023 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

/etc/resolvconf:
total 20
drwxr-xr-x  3 root root  4096 Aug 24  2022 .
drwxr-xr-x 88 root root 12288 Sep  3 19:59 ..
drwxr-xr-x  2 root root  4096 Aug 24  2022 update-libc.d
[\code]

And 
# nano /etc/resolv.conf 
[\code] 

opens empty file which I'm not able to save, with the error that the file does not exist.

Bobby,

> ~# ls -al /etc/resolv*
> lrwxrwxrwx 1 root root 39 Jul 23 2023
> /etc/resolv.conf ->
> ../run/systemd/resolve/stub-resolv.conf

I see. You are running systemd. So you need do it the systemd way, with systemd-resolved.

Quote

# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

-bash: resolvectl: command not found

And there is no stub-resolv.conf on my system, according to

find / -name *stub*

I don't use systemd on these small NAS. So perhaps others can help?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Debian Testing/Trixie removes systemd-resolved

The problem is in Debian bookworm, not trixie.

Quote
Bobby
I updated my NSA325 to Debian 12 and lost network connection

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> cat /etc/network/interfaces
>

> rename /end0=eth0
> 
> auto lo eth0
> iface lo inet loopback
> # primary network interface
> auto eth0
> iface eth0 inet static
>  address 192.168.2.21
>  netmask 255.255.255.0
>  gateway 192.168.2.1
>  dns-nameservers  8.8.8.8 8.8.4.4 1.1.1.1 
>

BTW, don't use 1.1.1.1 until you are sure you want to:

https://arstechnica.com/security/2025/09/mis-issued-certificates-for-1-1-1-1-dns-service-pose-a-threat-to-the-internet/

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/04/2025 03:27PM by bodhi.

Thanks for the pointers!

I found the solution. Turns out there has been a change in DNS resolver with Bookworm and more people hav had the same experience as I. In short:
- after upgarde to Debian 12 Bookworm you cannot apt update, because sources are not found
- Ping www.google.com gives the same image: webaddresses are not accessible
- Ping 8.8.8.8 does work so the internet connection itself is working and its a DNS problem
- cat /etc/resolve.conf gvies an empty file
- nano /etc/resolve.conf give an empty file to which you cannot save changes
- ls -al /etc/resolve.conf shows that there is only a symlink for the file

lrwxrwxrwx 1 root root   39 Jul 23  2023 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

- the solution was to remove the symlink

rm /etc/resolve.conf

- create /etc/resolve.conf with at least one working nameserver

nano /etc/resolve.conf

- add nameserver and save the file

 nameserver 8.8.8.8

- apt update && upgrade

And you're back to work!

All was in this link, but change 'nameserver 1.1.1.1'

https://forums.debian.net/viewtopic.php?p=774250

Quote

BTW, don't use 1.1.1.1 until you are sure you want to:

https://arstechnica.com/security/2025/09/mis-issued-certificates-for-1-1-1-1-dns-service-pose-a-threat-to-the-internet/

Edited 1 time(s). Last edit at 09/07/2025 02:49AM by Bobby.