One question is whether or not it is resolvconf's responsibility to
check upness of interfaces. Resolvconf is really just a registry.
Suppliers of nameserver information are responsible for updating the
information they have supplied. So the bug in this case is certainly
vpnc's.
Given that the bug exists and some maintainers are more responsive than
others, it's conceivable that a workaround could be implemented in
resolvconf.
But it would be a bit of a hack because resolvconf doesn't know for sure
what interfaces correspond to what records. Suppliers of nameserver
information run "resolvconf -a $X" for some value of X. By convention X
has the value "${INTERFACE}.${SUPPLIER}" but not all suppliers follow
this convention. So resolvconf can't be sure what interface should be
checked. If a workaround were implemented it would have to be narrowly
focussed on the vpnc case.
--
Thomas Hood
Debian resolvconf maintainers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/262650
Title:
resolvconf should not use dns info for interfaces that are down
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/262650/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
