Resolver ignores ndots option

Bug #1468836 reported by brammator on 2015-06-25
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glibc (Arch Linux)
New
Undecided
Unassigned
glibc (CentOS)
New
Undecided
Unassigned
glibc (Ubuntu)
Medium
Unassigned
libc (Debian)
New
Undecided
Unassigned

Bug Description

Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned from the DNS server then resolver always try another attempt with the original name extended by what is in search option.
For example, if you're looking for very.long.url.nowhere and there is a line "search ubuntu.com" in resolv.conf (or no such line at all, which gives out "search mydomain.tld" by default) you will get addres of server very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should occurs only for urls having less that ndots option dots in its name.

First mentioned there https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 but still not fixed.

lsb_release:
Description: Ubuntu 14.04.2 LTS
Release: 14.04
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jun 3 20:17 seq
 crw-rw---- 1 root audio 116, 33 Jun 3 20:17 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: Bochs Bochs
Package: linux (not installed)
PciMultimedia:

ProcFB:

ProcKernelCmdLine: root=LABEL=DOROOT ro
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.8.0-19-generic i686
UpgradeStatus: Upgraded to trusty on 2015-06-03 (21 days ago)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1468836

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-unstable/

Changed in linux (Ubuntu):
importance: Undecided → Medium

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

brammator (brammator) wrote :

Just tested it with newly installed 15.04-minimal, upgraded to 4.1.0-040100 kernel package. Bug is still here.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
brammator (brammator) on 2015-07-07
affects: linux (Ubuntu) → glibc (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers