Crumb
c/debian · by Megaf@lemmy.ml · 3y

NetworkManager setting "nameserver ::1" to resolv.conf no matter my settings.

Hi everyone, so I'm having this weird issue. No matter the DNS and IP settings I use in NetworkManager, it will always generate the same resolv.conf.

resolv.conf

# Generated by NetworkManager
nameserver ::1

IPv6 is disabled by the way.

14 points · 10 comments · view on lemmy.world

10 Comments

dcat@lemmy.world · 6 pts · 3y (1 reply)

is /etc/resolv.conf a symlink?

Megaf@lemmy.ml · 2 pts · 3y

I actually thought about that too, but it isn't.

#: file /etc/resolv.conf
/etc/resolv.conf: ASCII text
ABluManOnLemmy@feddit.nl · 4 pts · 3y (4 replies)

I'm not sure but this might have to do with systemd-resolved. You may want to disable it, that might fix your problem

Megaf@lemmy.ml · 2 pts · 3y (2 replies)

Thought about that too, but I don't have resolvd nor systemd-resolv or systemd-resolve active. Nor do I have avahi running. Interesting isn't it?

ABluManOnLemmy@feddit.nl · 2 pts · 3y (1 reply)

Do you have any DNS server on port 53? If so, could you check which process or application it is?

Megaf@lemmy.ml · 1 pts · 3y

Nope :( Neither dnsmasq nor bind are installed. Nothing on port 53 either.

thelastknowngod@lemm.ee · 1 pts · 3y

This is it.

Megaf@lemmy.ml · 2 pts · 3y

I just found this file, now sure if it's related or not.

$: cat /run/NetworkManager/resolv.conf
# Generated by NetworkManager
nameserver ::1

and

$: cat /run/NetworkManager/no-stub-resolv.conf
# Generated by NetworkManager
nameserver ::1

Edit: those are generated from the /etc/resolv.conf NM generates.

TCB13@lemmy.world · 1 pts · 3y (1 reply)

Move to ----> systemd-networkd 😉 . Btw check your system isn't also running something systemd-resolved that you probably will want to disable as you are using NM.

Megaf@lemmy.ml · 1 pts · 3y

I don't have systemd-resolved installed.

[ 0 ] root@blaster:~#: apt remove --purge --auto-remove systemd-resolved
Reading package lists...
Building dependency tree...
Reading state information...
Package 'systemd-resolved' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[ 0 ] root@blaster:~#: ps aux | grep systemd
root         496  0.0  0.3 103956 56616 ?        Ss   10:17   0:05 /lib/systemd/systemd-journald
root         520  0.0  0.0  27656  7352 ?        Ss   10:17   0:00 /lib/systemd/systemd-udevd
systemd+     807  0.0  0.0  90528  7188 ?        Ssl  10:17   0:00 /lib/systemd/systemd-timesyncd
message+     813  0.0  0.0  11956  6724 ?        Ss   10:17   0:05 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root         835  0.0  0.0  50060  8000 ?        Ss   10:17   0:00 /lib/systemd/systemd-logind
reglnx      6027  0.0  0.0  19868 11644 ?        Ss   10:19   0:01 /lib/systemd/systemd --user
reglnx      6107  0.0  0.0  11148  6744 ?        Ss   10:19   0:01 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
reglnx      6514  0.0  0.1 594632 17812 ?        Ssl  10:19   0:00 /usr/libexec/gnome-session-binary --systemd-service --session=gnome
root      639055  0.0  0.0   6332  2028 pts/1    S+   14:19   0:00 grep --color=auto systemd
[ 0 ] root@blaster:~#: