[Resolvconf-devel] From where does resolvonf "invents" these "bad" name servers ?
Pierre Couderc
pierre at couderc.eu
Mon Apr 3 16:55:22 UTC 2017
My resolv.conf generated by resolvconf, contains 2 unexpected (ipV6)
name servers, that - at my knowledge - are not in our local DHCP
(isc-dhcp-server, which at my knowledge is not ipv6 enabled).
and they are in 1rst position !
If I change manually resolv.conf it is quikcly modified again after a
few seconds or minutes.
Only eth1 is connected (eth0 is not linked to anything).
The question is : how can I trace "who" triggers resolvconf ? Is there a
log of resolvconf. I see nothing in syslog ?
What should I search with tcpdump ?
My network interface is :
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth0 inet6 auto
# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp
# This is an autoconfigured IPv6 interface
iface eth1 inet6 auto
And reslov.conf :*
*
couderc:~$ cat /etc/resolv.conf
domain couderc.eu
search couderc.eu
nameserver 2a01:e00::2
nameserver 2a01:e00::1
nameserver 192.168.163.3
nameserver 212.27.40.240
nameserver 5.9.49.12
nameserver 8.8.8.8
nameserver 212.27.40.241
nameserver 2a01:e00::2 and nameserver 2a01:e00::1 are my ISP DNSs, but
DHCP is not enabled on ISP box (french freebox).
More information about the Resolvconf-devel
mailing list