Package: dnssec-trigger
Version: 0.13~svn685-4
Severity: normal
Dear Maintainer,
I purged dnssec-trigger and found /etc/resolv.conf having the
following output :-
[$] cat /etc/resolv.conf
# Generated by dnssec-trigger 0.13
nameserver 127.0.0.1
I rebooted the service by :-
$ sudo systemctl networking restart
That didn't change the output.
I rebooted and that didn't change the output.
I saw this while browsing via journalctl :-
Apr 13 06:12:30 debian ufw[404]: Starting firewall: ufw...Setting
kernel variables (/etc/ufw/sysctl.conf)...done.
Apr 13 06:12:30 debian kbd[406]: Setting console screen modes.
Apr 13 06:12:30 debian kbd[406]: setterm: $TERM is not defined.
Apr 13 06:12:30 debian adjtimex[408]: Regulating system clock...done.
Apr 13 06:12:30 debian console-setup[473]: Setting up console font and
keymap...done.
--------
--------
Apr 13 06:12:33 debian dhclient[603]: DHCPREQUEST on eth0 to
255.255.255.255 port 67
Apr 13 06:12:33 debian networking[402]: DHCPREQUEST on eth0 to
255.255.255.255 port 67
Apr 13 06:12:33 debian dhclient[603]: DHCPACK from 192.168.1.1
Apr 13 06:12:33 debian networking[402]: DHCPACK from 192.168.1.1
Apr 13 06:12:33 debian networking[402]: mv: cannot move
'/etc/resolv.conf.dhclient-new' to '/etc/resolv.conf': Operation not
permitted
As can be seen somehow dhclient is now unable to write to /etc/resolv.conf :(
Please let me know if I forgot to add something.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
