[Resolvconf-devel] Bug#791978: interfaces-order is being ignored
Thomas Hood
jdthood at gmail.com
Fri Jul 10 20:50:04 UTC 2015
> resolvconf is not putting the tun0 resolvers
> below that of eth* even though tun* is supposed to take precedence
I don't understand this. If tun* is supposed to take precedence over eth*
then resolvconf *shouldn't* put the tun0 resolver addresses *below* those
of eth* in resolv.conf; resolvconf should put the tun0 resolver addresses
*above* those of eth*.
And resolvconf does what it should do. According to interface-order, tun*
is listed before eth*. The record /run/resolvconf/interface/tun0.f5
contains
nameserver 192.168.1.1
nameserver 10.10.10.21
nameserver 10.10.10.20
search canaccord.com
whereas the record /run/resolvconf/interface/eth0.f5 contains
search canaccord.com
nameserver 10.10.10.21
nameserver 10.10.10.20
and the record /run/resolvconf/interface/eth3.dhclient contains the
following.
nameserver 192.168.1.1
The information from tun0.f5 should take precedence. And that is what we
see in resolv.conf.
# Dynamic resolv.conf(5) file for glibc resolver(3) ...
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES ...
nameserver 192.168.1.1
nameserver 10.10.10.21
nameserver 10.10.10.20
search canaccord.com
If there is a problem then the problem is with the contents of the
record /run/resolvconf/interface/tun0.f5 which comes from the program
that calls resolvconf to create that record. Which interface
configuration utility writes that record? What is "f5"?
--
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20150710/fde8817e/attachment.html>
More information about the Resolvconf-devel
mailing list