dns resolv.cnf

Support Hardware
#1

**Briefly describe your issue below

How is everyone! I just had a weird thing happen. I booted up parrot after a system update and dns stopped working for me. After checking the router and everything I finally looked in var/log/syslog and found this:

Apr 23 21:25:53 xicamatl kernel: [   44.084125] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

**snip**

Apr 23 21:25:54 xicamatl NetworkManager[862]: [1587702354.0171] policy: set ‘flcl’ (wlan0) as default for IPv4 routing and DNS
Apr 23 21:25:54 xicamatl NetworkManager[862]: [1587702354.0175] dns-mgr: Writing DNS information to /sbin/resolvconf

important thing

Apr 23 21:25:54 xicamatl NetworkManager[1732]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf

Apr 23 21:25:54 xicamatl NetworkManager[862]: [1587702354.0405] device (wlan0): Activation: successful, device activated.
Apr 23 21:25:54 xicamatl NetworkManager[862]: [1587702354.0418] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 23 21:25:54 xicamatl systemd[1]: systemd-hostnamed.service: Succeeded.

/etc/resolv.conf turned out to have nothing in it except [something] 127.0.0.1

so I deleted it and symlinked to /run/resolvconf/resolv.conf and dns starting working

Does this make sense to anyone? How did things get like this?

The only thing I’d done was update the system (using GUI app)

What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)

latest and greatest

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)

standard, I think

Configured to multiboot with other systems? (yes / no)

sharing a mac Mini with Macos

List your hardware specs to include make, model and firmware (when applicable):?

2014 mac Mini

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

see above!

#2

I swapped it to a sym link to begin with but ended up with more issues than before.

I believe that anonsurf changes resolv.conf to 127.0.0.1 when it starts and moves the original settings to resolv.cnf.bak. When it stops, it’s supposed to change it back to what it was originally but I think theres a slight known issue where sometimes it doesn’t stop properly and the resolv.conf stays at 127.0.0.1. Doesn’t happen always, it’s intermittent.

I think I remember reading somewhere that it will be fixed in the next release - for the time being, I’ve created a little script that puts the dns settings right when it happens. I also created a little monitor that outputs the contents of resolv.cnf to my conky display so that I can clearly see when it occurs.

1 Like
#3

See https://community.parrotsec.org/t/anonsurf-ver-2-12-is-on-testing/12573

#4

This makes perfect sense. It just happened again, and it was after I’d shut down the machine while in anon surf. After starting (and stopping) anon surf the problem went away.

#5

Why does it seem like a system update problem? Because the system update prompt comes up after booting and (probably because of DNS problem) “finishes” immediately after it starts.