kppp does not prioritise DNS servers in resolv.conf correctly

Bug #53875 reported by Alexandros Papadopoulos
4
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/interfaces.

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/interfaces.

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.

Revision history for this message
Jim Qode (jimqode) wrote :

ns records added twice seems to be related to this bug:
http://bugs.kde.org/show_bug.cgi?id=15315

Revision history for this message
Jim Qode (jimqode) wrote :

Please include your distro version and kde version

Changed in kdenetwork:
status: New → Incomplete
Jim Qode (jimqode)
Changed in kdenetwork:
assignee: nobody → cem-sadecehosting
Revision history for this message
Ralph Janke (txwikinger) wrote :

According to the upstream report, this was fixed in 3.1.0. Could you please re-test this in a current version of Kubuntu?

Thanks

Changed in kdenetwork:
status: Unknown → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdenetwork:
status: Incomplete → Invalid
Changed in kdenetwork:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.