** Also affects: resolvconf (Nexenta Operating System)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1085756
Title:
/etc/ppp/ip-up.d/000resolvconf doesn't check if envvar USEPEERDNS is
set
Status in resolvconf package in Ubuntu:
Fix Released
Status in resolvconf package in Nexenta Operating System:
New
Bug description:
Description:
When running pppd without "usepeerdns", resolvconf's scripts will take the
DNS information from the IPCP.
In the script, it just checks to see if the DNS envvars are set and ignores
whether or not we actually want to use it.
In the PPP provided script 0000dns, it checks the USEPEERDNS envvar and
prevents this from happening.
Per PPP manpage:
"
Scripts
[..]
DNS1
If the peer supplies DNS server addresses, this variable is set to the first
DNS server address supplied.
DNS2
If the peer supplies DNS server addresses, this variable is set to the second
DNS server address supplied.
"
The script makes an assumption that DNS1 and DNS2 are only set if
"usepeerdns" is enabled, but manpage clearly indicates it will set
this envvar regardless of "usepeerdns" if IPCP receives them.
Conditions:
"usepeerdns" is not configured and IPCP provides DNS servers
Workaround:
chmod -x /etc/ppp/ip-up.d/000resolvconf
Affected versions:
Tested in precise but verified scripts the same in more recent releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1085756/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp