Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 116577 - search option of resolve.conf doesn't work just after reboot
Summary: search option of resolve.conf doesn't work just after reboot
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-23 22:57 UTC by Pavel B. Milovantsev
Modified: 2005-12-26 12:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel B. Milovantsev 2005-12-23 22:57:07 UTC
just after reboot server I have:

pav ~ # ssh gis
Password:
Last login: Sat Dec 24 12:53:07 2005 from pav.intis.tomsk.ru
gis ~ # cat /etc/resolv.conf
nameserver 192.168.44.1
search intis.tomsk.ru imces.ru
domain intis.tomsk.ru
gis ~ # ping -c1 pav
PING pav.intis.tomsk.ru (192.168.44.7) 56(84) bytes of data.
64 bytes from pav.intis.tomsk.ru (192.168.44.7): icmp_seq=1 ttl=64 time=0.110 ms

--- pav.intis.tomsk.ru ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.110/0.110/0.110/0.000 ms
gis ~ # ping -c1 ns
ping: unknown host ns
gis ~ # nano /etc/resolv.conf
gis ~ # cat /etc/resolv.conf
nameserver 192.168.44.1
domain intis.tomsk.ru
search intis.tomsk.ru imces.ru
gis ~ # ping -c1 pav
PING pav.intis.tomsk.ru (192.168.44.7) 56(84) bytes of data.
64 bytes from pav.intis.tomsk.ru (192.168.44.7): icmp_seq=1 ttl=64 time=0.114 ms

--- pav.intis.tomsk.ru ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.114/0.114/0.114/0.000 ms
gis ~ # ping -c1 ns
PING ns.imces.ru (84.237.1.129) 56(84) bytes of data.
64 bytes from imces.ru (84.237.1.129): icmp_seq=1 ttl=63 time=1.91 ms

--- ns.imces.ru ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.919/1.919/1.919/0.000 ms

===================MORE INFORMATION===============================

gis ~ # cat /etc/conf.d/hostname
# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/conf.d/hostname,v 1.2 2004/11/15 19:08:37 vapier Exp $

# Set to the hostname of this machine
HOSTNAME="gis"
gis ~ # cat /etc/conf.d/domainname
# /etc/conf.d/domainname

# When setting up resolv.conf, what should take precedence?
#  0 = let dhcp/whatever override DNSDOMAIN
#  1 = override dhcp/whatever with DNSDOMAIN

OVERRIDE=1

# To have a proper FQDN, you need to setup /etc/hosts and /etc/resolv.conf
# (domain entry in /etc/resolv.conf and FQDN in /etc/hosts).
#
# DNSDOMAIN merely sets the domain entry in /etc/resolv.conf, see
# the resolv.conf(5) manpage for more info.

DNSDOMAIN="intis.tomsk.ru"

# For information on setting up NIS, please see:
#   http://www.linux-nis.org/nis-howto/HOWTO/

NISDOMAIN=""
Comment 1 SpanKY gentoo-dev 2005-12-25 19:56:30 UTC
i dont really get what you're trying to say is wrong but the output you've shown is the expected behavior
Comment 2 Pavel B. Milovantsev 2005-12-26 00:01:55 UTC
Seems to me that comments about OVERRIDE should show that reslove.conf:search option will not work after reboot if this parameter is equal 1.

From other hand I didn't see anywhere that order of _LINES_ (not search option paramenters) in resolve.conf should affect resolver functionality.

Sorry, if I'm wrong. Feel free to close the bug, since I made OVERRIDE=0 and generated after reboot resolve.conf file have suitable for resolver LINES ORDER:

gis ~ # cat /etc/resolv.conf
domain intis.tomsk.ru
nameserver 192.168.44.1
search intis.tomsk.ru imces.ru
Comment 3 SpanKY gentoo-dev 2005-12-26 12:57:23 UTC
> From other hand I didn't see anywhere that order of _LINES_ (not search option
> paramenters) in resolve.conf should affect resolver functionality.

you didnt read the resolv.conf(5) manpage then like the domainname file told you to ... there's clearly a section which states:
       The domain and search keywords are mutually exclusive.   If  more  than
       one instance of these keywords is present, the last instance wins.