Resolver ignores ndots option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Arch Linux) |
New
|
Undecided
|
Unassigned | ||
glibc (CentOS) |
New
|
Undecided
|
Unassigned | ||
glibc (Ubuntu) |
Confirmed
|
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.
First mentioned there https:/
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
ProcVersionSign
RelatedPackageV
linux-
linux-
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:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
affects: | linux (Ubuntu) → glibc (Ubuntu) |
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.