kppp does not prioritise DNS servers in resolv.conf correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Network |
Invalid
|
Medium
|
|||
kdenetwork (Ubuntu) |
Invalid
|
Undecided
|
Jim Qode |
Bug Description
Binary package hint: kppp
99% of the times I use ethernet connections. Due to bug #25624 I've manually added dns-nameservers nnn.nnn.nnn.nnn to the interface stanzas of my connections in /etc/network/
But when I need to use a dialup connection with kppp, after connecting it only adds the nameservers provided by my ISP *below* the static nameserver I've denoted in /etc/network/
As a result, as soon as KPPP connects, /etc/resolv.conf looks as follows:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver nnn.nnn.nnn.nnn <= This is my ethernet DNS!
nameserver aaa.aaa.aaa.aaa
nameserver bbb.bbb.bbb.bbb
nameserver aaa.aaa.aaa.aaa #KPPP temporary entry
nameserver bbb.bbb.bbb.bbb #KPPP temporary entry
As a result, nnn.nnn.nnn.nnn which is not reachable in this scenario is queried for DNS records, and networking hangs indefinitely.
KPPP should add its temporary entries to the top of the nameservers list.
The fact that the two nameserver provided by my ISP are added twice to /etc/resolv.conf is a harmless bug, as they are removed properly on disconnection.
Changed in kdenetwork: | |
assignee: | nobody → cem-sadecehosting |
Changed in kdenetwork: | |
status: | Unknown → Invalid |
Changed in kdenetwork: | |
importance: | Unknown → Medium |
ns records added twice seems to be related to this bug: bugs.kde. org/show_ bug.cgi? id=15315
http://